Facundo Batista wrote: > 2008/11/17 Barry Warsaw <barry at python.org>: > >> Martin suggests, and I agree, that we should release Python 3.0 final and >> 2.6.1 at the same time. Makes sense to me. That would mean that Python >> 2.6.1 should be ready on 03-Dec (well, if Python 3.0 is ready then!). > > 2.6.1 only two months after 2.6? Why so quickly? > > Anyway, I don't see any added value in the synchronization, so taking > in consideration all the effort you're putting in these releases, I > would just want to minimize your workload... which is easier to you? > doing both at the same time or not? There have been several corrections made to the 2to3 conversion tool - it would be good to get those in developer's hands at the same time that 3.0 final becomes available. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia ---------------------------------------------------------------
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4