A.M. Kuchling amk at amk.ca
Tue Oct 7 15:03:46 CEST 2008

• Previous message: [python-committers] [Python-3000] [Python-Dev] Proposed Python 3.0 schedule
• Next message: [python-committers] [Python-Dev] Proposed Python 3.0 schedule
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On Tue, Oct 07, 2008 at 09:20:23AM -0300, Facundo Batista wrote:
> I don't want to keep deferring 3.0 months and months, I prefer to have
> a redesigned schedule now, and stick to it as much as possible, even
> if the 3.0 version is not as robust as we would want.

Another, related policy issue: must 3.1 be compatible with 3.0?  Or is
3.0 an experimental version in some respects (for example, the stdlib)
and 3.1 the 'final' version?

--amk

---

• Previous message: [python-committers] [Python-3000] [Python-Dev] Proposed Python 3.0 schedule
• Next message: [python-committers] [Python-Dev] Proposed Python 3.0 schedule
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the python-committers mailing list