[RELEASED] Python 3.4.0 release candidate 1
On behalf of the Python development team, I'm delighted to announce the first release candidate of Python 3.4. This is a preview release, and its use is not recommended for production settings. Python 3.4 includes a range of improvements of the 3.x series, including hundreds of small improvements and bug fixes. Major new features and changes in the 3.4 release series include: * PEP 428, a "pathlib" module providing object-oriented filesystem paths * PEP 435, a standardized "enum" module * PEP 436, a build enhancement that will help generate introspection information for builtins * PEP 442, improved semantics for object finalization * PEP 443, adding single-dispatch generic functions to the standard library * PEP 445, a new C API for implementing custom memory allocators * PEP 446, changing file descriptors to not be inherited by default in subprocesses * PEP 450, a new "statistics" module * PEP 451, standardizing module metadata for Python's module import system * PEP 453, a bundled installer for the *pip* package manager * PEP 454, a new "tracemalloc" module for tracing Python memory allocations * PEP 456, a new hash algorithm for Python strings and binary data * PEP 3154, a new and improved protocol for pickled objects * PEP 3156, a new "asyncio" module, a new framework for asynchronous I/O Python 3.4 is now in "feature freeze", meaning that no new features will be added. The final release is projected for mid-March 2014. To download Python 3.4.0rc1 visit: http://www.python.org/download/releases/3.4.0/ Please consider trying Python 3.4.0rc1 with your code and reporting any new issues you notice to: http://bugs.python.org/ Enjoy! -- Larry Hastings, Release Manager larry at hastings.org (on behalf of the entire python-dev team and 3.4's contributors)
Hi, It would be nice to give also the link to the whole changelog in your emails and on the website: http://docs.python.org/3.4/whatsnew/changelog.html Congrats for your RC1 release :-) It's always hard to make developers stop addings "new minor" changes before the final version :-) Victor 2014-02-11 8:43 GMT+01:00 Larry Hastings <larry@hastings.org>:
On behalf of the Python development team, I'm delighted to announce the first release candidate of Python 3.4.
This is a preview release, and its use is not recommended for production settings.
Python 3.4 includes a range of improvements of the 3.x series, including hundreds of small improvements and bug fixes. Major new features and changes in the 3.4 release series include:
* PEP 428, a "pathlib" module providing object-oriented filesystem paths * PEP 435, a standardized "enum" module * PEP 436, a build enhancement that will help generate introspection information for builtins * PEP 442, improved semantics for object finalization * PEP 443, adding single-dispatch generic functions to the standard library * PEP 445, a new C API for implementing custom memory allocators * PEP 446, changing file descriptors to not be inherited by default in subprocesses * PEP 450, a new "statistics" module * PEP 451, standardizing module metadata for Python's module import system * PEP 453, a bundled installer for the *pip* package manager * PEP 454, a new "tracemalloc" module for tracing Python memory allocations * PEP 456, a new hash algorithm for Python strings and binary data * PEP 3154, a new and improved protocol for pickled objects * PEP 3156, a new "asyncio" module, a new framework for asynchronous I/O
Python 3.4 is now in "feature freeze", meaning that no new features will be added. The final release is projected for mid-March 2014.
To download Python 3.4.0rc1 visit:
http://www.python.org/download/releases/3.4.0/
Please consider trying Python 3.4.0rc1 with your code and reporting any new issues you notice to:
Enjoy!
-- Larry Hastings, Release Manager larry at hastings.org (on behalf of the entire python-dev team and 3.4's contributors) _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/victor.stinner%40gmail.co...
[32-bit Windows XP-SP2] Python 3.4.0rc1's MSI installer won't install on my machine. Error message (typed in from screenshot): ''' There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. ''' I tried to install twice with the default options as well as once with the pip option deselected -- all errored out with the above message. (And yes, I did delete the entire Python34 directory before trying to install. :-) ) As I experienced trouble with Python 3.4.0b2's installer, not sure if the problem is here or with the installer. (But b2 did install and seem to be okay.) Bob Hanson
Hi, 2014-02-12 17:30 GMT+01:00 Bob Hanson <d2mp1a9@newsguy.com>:
[32-bit Windows XP-SP2]
Python 3.4.0rc1's MSI installer won't install on my machine.
I justed tested Python 3.4.0rc1 MSI installer on Windows XP SP3 (32-bit): Python was installed successfully. Victor
On Wed, 12 Feb 2014 17:42:49 +0100, Victor Stinner wrote:
2014-02-12 17:30 GMT+01:00 Bob Hanson <d2mp1a9@newsguy.com>:
[32-bit Windows XP-SP2]
Python 3.4.0rc1's MSI installer won't install on my machine.
I justed tested Python 3.4.0rc1 MSI installer on Windows XP SP3 (32-bit): Python was installed successfully.
Does this mean that Python no longer supports XP-SP2? Bob Hanson
2014-02-12 18:10 GMT+01:00 Bob Hanson <d2mp1a9@newsguy.com>:
Does this mean that Python no longer supports XP-SP2?
I don't know what it means. I don't have access to Windows XP SP2 to test. By the way, why not upgrading to SP3? :-) I read that you installed the beta2 before. You should maybe make sure that Python 3.4 beta 2 has been fully uninstalled. Why did you remove the directory manually? Why not uninstall using the Control Panel? Victor
TL;DR: Solved. Thanks, Victor, for prodding me to jump through all those Windows hoops. ;-) [More comments interleaved below:] On Wed, 12 Feb 2014 18:15:43 +0100, Victor Stinner wrote:
2014-02-12 18:10 GMT+01:00 Bob Hanson <d2mp1a9@newsguy.com>:
By the way, why not upgrading to SP3? :-)
Lots of reasons. One, though, IIRC, MS does not allow downloads of such anymore. (More importantly to me, I don't like the EULA for SP3+ and don't want to implicitly agree to it.)
I read that you installed the beta2 before. You should maybe make sure that Python 3.4 beta 2 has been fully uninstalled. Why did you remove the directory manually? Why not uninstall using the Control Panel?
'Twas long years of fighting with the Add/Remove Programs applet when working with Python and other OSS which made me do the "naughty" thing today. In my experience, particularly if one has third-party packages installed by a variety of means, the Control Panel applet often screws things up royally when "removing" things. (Also, I'd just read about Terry's install problems -- usually, I just install overtop the prior version and the MSI installer does the right thing. Today, though, with the above paragraph in mind, and with Terry's problems, I just decided to "shortcut" things.) Following Victor's questioning, I put the dir back, went to CP and did the Add/Remove thing, and then reinstalled rc1 and it "worked." Perhaps a caution in the docs (release notes?) or some such should be added -- as far as I know, I used to be able to delete Python dirs with abandon before installing a different version. It *does* seem that Python and Windows is becoming a sadder story -- I know, use Linux. :-) Meanwhile, my main Python remains 2.5.4 -- a very good vintage. Anyway, thanks again, Victor, for encouraging me to do the obstacle course yet again. :-) Bob Hanson
On 13 Feb 2014 04:06, "Bob Hanson" <d2mp1a9@newsguy.com> wrote:
TL;DR: Solved. Thanks, Victor, for prodding me to jump through all those Windows hoops. ;-)
[More comments interleaved below:]
On Wed, 12 Feb 2014 18:15:43 +0100, Victor Stinner wrote:
2014-02-12 18:10 GMT+01:00 Bob Hanson <d2mp1a9@newsguy.com>:
By the way, why not upgrading to SP3? :-)
Lots of reasons. One, though, IIRC, MS does not allow downloads of such anymore.
(More importantly to me, I don't like the EULA for SP3+ and don't want to implicitly agree to it.)
I read that you installed the beta2 before. You should maybe make sure that Python 3.4 beta 2 has been fully uninstalled. Why did you remove the directory manually? Why not uninstall using the Control Panel?
'Twas long years of fighting with the Add/Remove Programs applet when working with Python and other OSS which made me do the "naughty" thing today. In my experience, particularly if one has third-party packages installed by a variety of means, the Control Panel applet often screws things up royally when "removing" things.
(Also, I'd just read about Terry's install problems -- usually, I just install overtop the prior version and the MSI installer does the right thing. Today, though, with the above paragraph in mind, and with Terry's problems, I just decided to "shortcut" things.)
Following Victor's questioning, I put the dir back, went to CP and did the Add/Remove thing, and then reinstalled rc1 and it "worked."
Perhaps a caution in the docs (release notes?) or some such should be added -- as far as I know, I used to be able to delete Python dirs with abandon before installing a different version.
Just deleting the Python directory hasn't been the right thing to do in a very long time - it leaves cruft in the registry at the very least (that will confuse other tools into thinking Python is still installed), and since Python 3.3 will also leave the Python Launcher for Windows installed. Using Add/Remove programs instead of just deleting directories is a general Windows administration requirement for MSI installers, so there's no reason to add a specific note.
It *does* seem that Python and Windows is becoming a sadder story -- I know, use Linux. :-)
Actually, we've been substantially improving the Windows integration to make things easier for new users, which is the main reason the Windows installer has become substantially less tolerant of corruption of the registry state (which is effectively what occurs when you just delete the Python directory instead of uninstalling it through Add/Remove programs). Python 3.4 now not only provides the "py" multi-version launcher and the "pip" package installer, selecting the path modification component during installation means you don't even need to adjust PATH yourself any more. The primary beneficiaries of the increasing adoption of the pre-built wheel binary packaging format are also Windows users (Linux users and Mac OS X users that do not use the python.org binaries currently still need to build from source themselves, or bootstrap the cross-platform conda tools).
Meanwhile, my main Python remains 2.5.4 -- a very good vintage.
If that's your baseline, then yes, Python was likely still quite tolerant of bypassing the uninstallation process back then. That hasn't been the case for a long time. Regards, Nick.
Anyway, thanks again, Victor, for encouraging me to do the obstacle course yet again. :-)
Bob Hanson
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe:
https://mail.python.org/mailman/options/python-dev/ncoghlan%40gmail.com
On 12 February 2014 20:38, Nick Coghlan <ncoghlan@gmail.com> wrote:
It *does* seem that Python and Windows is becoming a sadder story -- I know, use Linux. :-)
Actually, we've been substantially improving the Windows integration to make things easier for new users, which is the main reason the Windows installer has become substantially less tolerant of corruption of the registry state (which is effectively what occurs when you just delete the Python directory instead of uninstalling it through Add/Remove programs).
Agreed, I feel that the user's experience of Python on Windows has been steadily improving. Thanks to everyone for this. The one thing that I sometimes miss is a "portable" distribution (i.e., unzip and run, do any PATH manipulation etc that you want yourself). But it's easy to make one yourself, so no real issue there. Paul
On 2/12/2014 3:38 PM, Nick Coghlan wrote:
Just deleting the Python directory hasn't been the right thing to do in a very long time - it leaves cruft in the registry at the very least (that will confuse other tools into thinking Python is still installed), and since Python 3.3 will also leave the Python Launcher for Windows installed.
Using Add/Remove programs instead of just deleting directories is a general Windows administration requirement for MSI installers, so there's no reason to add a specific note.
In windows 7, Add/Remove is not Programs and Features. Looking there, I found an entry for .0b2 that should have been removed by the .0b3 install, but was not. When I tried to uninstall .0b2, I got the same box about not being able to run something. I downloaded the .0b2 installer from www.python.org/ftp/python/3.4.0/, repaired the .0b2 installation, and then uninstalled it, and the entry disappeared. I was then able to install 64bit .0c1. So I conclude that a glitch in the .0b3 installation, leaving a bit of .0b2, made .0c1 unable to uninstall .0b3 properly. -- Terry Jan Reedy
On 02/12/2014 10:30 AM, Bob Hanson wrote:
[32-bit Windows XP-SP2]
Python 3.4.0rc1's MSI installer won't install on my machine.
Error message (typed in from screenshot):
''' There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. '''
Bob Hanson
I've seen an error message similar to this one, because I didn't run the installer as admin. ('Run as Administrator...'). Not sure if its the same thing here though. -- \¯\ /¯/\ \ \/¯¯\/ / / Christopher Welborn (cj) \__/\__/ / cjwelborn at live·com \__/\__/ http://welbornprod.com
On Wed, 12 Feb 2014 11:49:20 -0600, Christopher Welborn wrote:
I've seen an error message similar to this one, because I didn't run the installer as admin. ('Run as Administrator...'). Not sure if its the same thing here though.
Thanks for the suggestion, Christopher. However, see my last reply to Victor up-thread -- the problem is now solved, I think. (I had to use the Windows Add/Remove programs applet to fix things.) Bob Hanson
participants (7)
-
Bob Hanson -
Christopher Welborn -
Larry Hastings -
Nick Coghlan -
Paul Moore -
Terry Reedy -
Victor Stinner