On 2 Mar, 10:02, Kay Schluehr [EMAIL PROTECTED] wrote:
On 2 Mrz., 06:53, Ben Finney [EMAIL PROTECTED]
wrote:
One of the stated goals of the migration is that the '2to3' program
will only migrate Python 2.6 code - Python 3.0 code.
Yes, I know. Why?
The master said so isn't an entirely
On Mar 1, 10:53 pm, Kay Schluehr [EMAIL PROTECTED] wrote:
On 1 Mrz., 19:51, Barry Warsaw [EMAIL PROTECTED] wrote:
Python 2.6 is not only the next advancement in the Python 2 series, it
is also a transitionary release, helping developers begin to prepare
their code for Python 3.0.
Isn't
On Mar 1, 10:53 pm, Kay Schluehr [EMAIL PROTECTED] wrote:
On 1 Mrz., 19:51, Barry Warsaw [EMAIL PROTECTED] wrote:
Python 2.6 is not only the next advancement in the Python 2 series, it
is also a transitionary release, helping developers begin to prepare
their code for Python 3.0.
Isn't
Tim Roberts [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
| Kay Schluehr [EMAIL PROTECTED] wrote:
| The master said so isn't an entirely satisfying answer.
|
| Nevertheless, it IS the answer for many questions in the Python world.
But not for the questions about 2to3
Current 2to3
On 2 Mrz., 06:53, Ben Finney [EMAIL PROTECTED]
wrote:
One of the stated goals of the migration is that the '2to3' program
will only migrate Python 2.6 code - Python 3.0 code.
Yes, I know. Why?
The master said so isn't an entirely satisfying answer. What are the
*technical reasons* that make
On Mar 2, 4:02 am, Kay Schluehr [EMAIL PROTECTED] wrote:
On 2 Mrz., 06:53, Ben Finney [EMAIL PROTECTED]
wrote:
One of the stated goals of the migration is that the '2to3' program
will only migrate Python 2.6 code - Python 3.0 code.
Yes, I know. Why?
The master said so isn't an entirely
Kay Schluehr [EMAIL PROTECTED] writes:
On 2 Mrz., 06:53, Ben Finney [EMAIL PROTECTED]
wrote:
One of the stated goals of the migration is that the '2to3'
program will only migrate Python 2.6 code - Python 3.0 code.
Yes, I know. Why?
The master said so isn't an entirely satisfying
Kay Schluehr [EMAIL PROTECTED] wrote:
On 2 Mrz., 06:53, Ben Finney [EMAIL PROTECTED]
wrote:
One of the stated goals of the migration is that the '2to3' program
will only migrate Python 2.6 code - Python 3.0 code.
Yes, I know. Why?
The master said so isn't an entirely satisfying answer.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On behalf of the Python development team and the Python community, I'm
happy to announce the first alpha release of Python 2.6, and the third
alpha release of Python 3.0.
Python 2.6 is not only the next advancement in the Python 2 series, it
is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On behalf of the Python development team and the Python community, I'm
happy to announce the first alpha release of Python 2.6, and the third
alpha release of Python 3.0.
Python 2.6 is not only the next advancement in the Python 2 series, it
is
As of 4:50 PM EST, the links to Windows installers give 404 File Not
Found.
I gather that they are still in process,
and notice that there is no public c.l.p. announcement.
I just fixed that. The files were there; just the links were wrong.
Regards,
Martin
--
On 01/03/2008, Martin v. Löwis [EMAIL PROTECTED] wrote:
As of 4:50 PM EST, the links to Windows installers give 404 File Not
Found.
I gather that they are still in process,
and notice that there is no public c.l.p. announcement.
I just fixed that. The files were there; just the
The 2.6a1 x86 MSI is there, but the 3.0a3 x86 MSI is still giving a 404.
Please try again - *those* files weren't actually there when I sent my
last message; I just built them.
Regards,
Martin
--
http://mail.python.org/mailman/listinfo/python-list
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 1, 2008, at 5:26 PM, Martin v. Löwis wrote:
As of 4:50 PM EST, the links to Windows installers give 404 File Not
Found.
I gather that they are still in process,
and notice that there is no public c.l.p. announcement.
I just fixed that.
On 1 Mrz., 19:51, Barry Warsaw [EMAIL PROTECTED] wrote:
Python 2.6 is not only the next advancement in the Python 2 series, it
is also a transitionary release, helping developers begin to prepare
their code for Python 3.0.
Isn't this a silly idea? People have to migrate from 2.5 or lower
Kay Schluehr [EMAIL PROTECTED] writes:
On 1 Mrz., 19:51, Barry Warsaw [EMAIL PROTECTED] wrote:
Python 2.6 is not only the next advancement in the Python 2 series, it
is also a transitionary release, helping developers begin to prepare
their code for Python 3.0.
Isn't this a silly
Kay Schluehr [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
| On 1 Mrz., 19:51, Barry Warsaw [EMAIL PROTECTED] wrote:
|
| Python 2.6 is not only the next advancement in the Python 2 series, it
| is also a transitionary release, helping developers begin to prepare
| their code for
17 matches
Mail list logo
