Python 3.0 (pinin' for the fjords)

[Barry Warsaw]

Now that Python 3.1 is out, it seems there's been some confusion as to
whether there will be one last Python 3.0 release, i.e. Python 3.0.2.

At the PyCon 2009 language summit it was decided that there will be
*no* Python 3.0.2. Python 3.0 is different than all other releases.
There will be no last maintenance release and no ongoing security
releases. Python 3.1 is the replacement for Python 3.0, and it's
release schedule was accelerated specifically so that production users
would be able to switch immediately.

If you're using Python 3, you are strongly urged to update to Python
3.1. Python 3.1 will be a 'normal' release in that we're making all
the guarantees that we make for other releases. It is likely that
Python 3.2 is 18-24 months away, there will be Python 3.1.x
maintenance releases, and there will be one last Python 3.1.x release
after the final release of Python 3.2.

Cheers,
-Barry


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)

iQIcBAEBCAAGBQJKTT5vAAoJEBJutWOnSwa/w/oP/icJzMuOkRdmUAlqY77BeAWE
MmoBe2Jo50qciAbVqvGgDB5S/MMes+aNHkyluiaRTRAdD8AdK0ZWFJwn+NzJcNxu
7vsn2xEaFKQMmOAoGcm3gH1GgyGRz7mVaPbjarASdL7dp0/EQcX62ZAkcr3zRZZw
M7/DNNKshd3N7EBE1hBc3O4zDJ5DpWCMmY+xwbAuQpW/9VKuJxlNtlyRyX5dfyet
JPft3cWMz/8c7pICKKHGQ+mct7tCPRZ57KBkCKerkhqr9Q1A7dBMRcqtFvSq9pPd
VgKo7DA+Q/1dBY5QmGmH6PvEigoQG4obnzQLYDjnLCbys8frVSTZN6xbrBKSyTb4
N7I/1zQRc7PQnFrJPz1wIL28KR6xP54dA1HJ/ebVGyekF0xT6yf/z/hAGO3LvRuu
7EqjHYfuC50Cc6G84NM2asWzaaGXIrVD6da0sCdJVkxqday5g5g+aM1LHczc95y4
/Z/lBC/bGQnmOVLgve8FMA0rJMYBQX9AFXRwAR353SfccQYBA7kkQTmO2UgzWVYh
/v1QBUsQfhHAcVnO288qvRiHMbvqr9WsHQP/byxqPADbEp492vQlRk+DytX4KNW3
3NmgpDZvicsSER0GgZSFFi8Lm7sGaj+LhDoNp8iYyUXXO3HBq4re2apglXjUpMFH
F1QHcbxyIOHm5huM3jQp
=SYB1
-----END PGP SIGNATURE-----

 

[Alan G Isaac]

Using the 3.1 Windows installer, I chose that I did not
want the extensions registered, and the installer
unregistered the .py and .pyw extensions (which I had wanted
to keep associated with Python 2.6).

Is this intentional?

Alan Isaac

PS I already fixed the problem. My question
is about intent.

 

[Terry Reedy]

Using the 3.1 Windows installer, I chose that I did not
want the extensions registered, and the installer
unregistered the .py and .pyw extensions (which I had wanted
to keep associated with Python 2.6).

Is this intentional?

I suspect not, but Martin is the one to answer.
If you had started a new thread for this new topic
"3.1 Windows Installer trashes extension registrations"
this would have been seen more easily ;-)

 

[Alan G Isaac]

I suspect not, but Martin is the one to answer.
If you had started a new thread for this new topic
"3.1 Windows Installer trashes extension registrations"
this would have been seen more easily ;-)

Done.

Cheers,
Alan Isaac