A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2008-November/083584.html below:

[Python-Dev] [Python-3000] 2.6.1 and 3.0

[Python-Dev] [Python-3000] 2.6.1 and 3.0 [Python-Dev] [Python-3000] 2.6.1 and 3.0Facundo Batista facundobatista at gmail.com
Tue Nov 18 11:03:02 CET 2008
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?

Regards,

-- 
.    Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
More information about the Python-Dev mailing list

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