[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) -- https://mail.python.org/mailman/listinfo/python-announce-list Support the Python Software Foundation: http://www.python.org/psf/donations/
Re: [RELEASED] Python 3.4.0 release candidate 1
[32-bit Windows XP-SP2] On Tue, 11 Feb 2014 12:11:49 -0500, Terry Reedy wrote: [problems installing rc1] On 2/11/2014 10:42 AM, Duncan Booth wrote: Does it put any useful messages in logfile.txt? 'error' occurs on 40. most are like the following MSI (s) (40:08) [11:57:25:973]: Package to be registered: 'python-3.4.0rc1.amd64.msi' MSI (s) (40:08) [11:57:25:973]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (40:08) [11:57:25:973]: Note: 1: 2262 2: AdminProperties 3: -2147287038 Here is the one for the boxed message: Action 11:57:26: RemovePip. Action start 11:57:26: RemovePip. MSI (s) (40:0C) [11:57:26:426]: Note: 1: 1721 2: RemovePip 3: C:\Programs\Python34\python.exe 4: -m ensurepip._uninstall MSI (s) (40:0C) [11:57:26:426]: Note: 1: 2262 2: Error 3: -2147287038 Error 1721. 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. Action: RemovePip, location: C:\Programs\Python34\python.exe, command: -m ensurepip._uninstall MSI (s) (40:0C) [11:57:28:874]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (40:0C) [11:57:28:874]: Product: Python 3.4.0b2 (64-bit) -- Error 1721. 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. Action: RemovePip, location: C:\Programs\Python34\python.exe, command: -m ensurepip._uninstall MSI (c) (98:EC) [11:57:30:204]: PROPERTY CHANGE: Deleting SECONDSEQUENCE property. Its current value is '1'. Action ended 11:57:30: ExecuteAction. Return value 3. MSI (c) (98:EC) [11:57:30:204]: Doing action: FatalError A Can you make anything of these? Interesting. I just had problems trying to install the 32-bit rc1 (see thread in py-dev; I think it's now solved). Here's what Windows Event Viewer said: ''' Product: Python 3.4.0b3 -- Error 1721. 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. Action: RemovePip, location: C:\Python34\python.exe, command: -m ensurepip._uninstall ''' Not sure why the installers are complaining about 3.4.0b3...? Pip seems to be figuring into these glitches, somehow...? (Note that both Terry and I are longtime Windows users, so likely we're both using our own procedures which *have* worked for years.) Bob Hanson -- Confucius say, Never, ever, make apps dependent on the Windows Registry. -- https://mail.python.org/mailman/listinfo/python-list
Re: [RELEASED] Python 3.4.0 release candidate 1
On 2/12/2014 2:42 PM, Bob Hanson wrote: [32-bit Windows XP-SP2] On Tue, 11 Feb 2014 12:11:49 -0500, Terry Reedy wrote: [problems installing rc1] On 2/11/2014 10:42 AM, Duncan Booth wrote: Does it put any useful messages in logfile.txt? 'error' occurs on 40. most are like the following MSI (s) (40:08) [11:57:25:973]: Package to be registered: 'python-3.4.0rc1.amd64.msi' MSI (s) (40:08) [11:57:25:973]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (40:08) [11:57:25:973]: Note: 1: 2262 2: AdminProperties 3: -2147287038 Here is the one for the boxed message: Action 11:57:26: RemovePip. Action start 11:57:26: RemovePip. MSI (s) (40:0C) [11:57:26:426]: Note: 1: 1721 2: RemovePip 3: C:\Programs\Python34\python.exe 4: -m ensurepip._uninstall MSI (s) (40:0C) [11:57:26:426]: Note: 1: 2262 2: Error 3: -2147287038 Error 1721. 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. Action: RemovePip, location: C:\Programs\Python34\python.exe, command: -m ensurepip._uninstall MSI (s) (40:0C) [11:57:28:874]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (40:0C) [11:57:28:874]: Product: Python 3.4.0b2 (64-bit) -- Error 1721. 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. Action: RemovePip, location: C:\Programs\Python34\python.exe, command: -m ensurepip._uninstall MSI (c) (98:EC) [11:57:30:204]: PROPERTY CHANGE: Deleting SECONDSEQUENCE property. Its current value is '1'. Action ended 11:57:30: ExecuteAction. Return value 3. MSI (c) (98:EC) [11:57:30:204]: Doing action: FatalError A Can you make anything of these? Interesting. I just had problems trying to install the 32-bit rc1 (see thread in py-dev; I think it's now solved). Here's what Windows Event Viewer said: ''' Product: Python 3.4.0b3 -- Error 1721. 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. Action: RemovePip, location: C:\Python34\python.exe, command: -m ensurepip._uninstall ''' Not sure why the installers are complaining about 3.4.0b3...? Pip seems to be figuring into these glitches, somehow...? (Note that both Terry and I are longtime Windows users, so likely we're both using our own procedures which *have* worked for years.) In my case, the problem appears to be that 3.4.0b3 did not completely uninstall and overwrite .0b2. Control Panel / Programs and Features (new name for Add/Remove) had entries for both .0b2 and .0b3, which it should not have. Trying to uninstall .0b2 gave same message. So I re-downloaded the .0b2 file from python.org/ftp/python/3.4.0, repaired .0b2, and then uninstalled it. The 64 bit .0c1 then seems to have installed Ok. -- Terry Jan Reedy -- https://mail.python.org/mailman/listinfo/python-list
Re: [RELEASED] Python 3.4.0 release candidate 1
On 2/11/2014 2:43 AM, Larry Hastings wrote: On behalf of the Python development team, I'm delighted to announce the first release candidate of Python 3.4. To download Python 3.4.0rc1 visit: http://www.python.org/download/releases/3.4.0/ I installed 64 bit 3.3.4 yesterday with no problem. I reran it today in repair mode and again, no problem. With 64 bit 3.4.0, I get There is a problem with this Windows Installer package. A program required for the install to complete could not be run. No, the generic message does not bother to say *which* program :-(. 34 bit 3.4.0 installed fine. I redownloaded 64bit 3.4.0 and install gives the same message. Can someone verify that this is not some bizarre glitch on my machine? If it is not, Windows users should download the 32 bit binary for now. Someone should remove the link to the installer that does not work. A followup should be posted when it is replaced. -- Terry Jan Reedy -- https://mail.python.org/mailman/listinfo/python-list
Re: [Python-Dev] [RELEASED] Python 3.4.0 release candidate 1
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 la...@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: 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) ___ Python-Dev mailing list python-...@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/victor.stinner%40gmail.com -- https://mail.python.org/mailman/listinfo/python-list
Re: [RELEASED] Python 3.4.0 release candidate 1
On 2/11/2014 5:13 AM, Terry Reedy wrote: On 2/11/2014 2:43 AM, Larry Hastings wrote: On behalf of the Python development team, I'm delighted to announce the first release candidate of Python 3.4. To download Python 3.4.0rc1 visit: http://www.python.org/download/releases/3.4.0/ I installed 64 bit 3.3.4 yesterday with no problem. I reran it today in repair mode and again, no problem. With 64 bit 3.4.0, I get There is a problem with this Windows Installer package. A program required for the install to complete could not be run. No, the generic message does not bother to say *which* program :-(. 34 bit 3.4.0 installed fine. I wrote too soon. Python 3.4.0rc1 (v3.4.0rc1:5e088cea8660, Feb 11 2014, 05:54:25) [MSC import tkinter Traceback ... import _tkinter ImportError: DLL load failed: %1 is not a valid Win32 application. So tkinter, Idle, turtle fail and the corresponding tests get skipped. -- Terry Jan Reedy -- https://mail.python.org/mailman/listinfo/python-list
Re: [RELEASED] Python 3.4.0 release candidate 1
On Tue, Feb 11, 2014 at 5:45 AM, Terry Reedy tjre...@udel.edu wrote: On 2/11/2014 5:13 AM, Terry Reedy wrote: ... I installed 64 bit 3.3.4 yesterday with no problem. I reran it today in repair mode and again, no problem. With 64 bit 3.4.0, I get There is a problem with this Windows Installer package. A program required for the install to complete could not be run. No, the generic message does not bother to say *which* program :-(. 34 bit 3.4.0 installed fine. I wrote too soon. Python 3.4.0rc1 (v3.4.0rc1:5e088cea8660, Feb 11 2014, 05:54:25) [MSC import tkinter Traceback ... import _tkinter ImportError: DLL load failed: %1 is not a valid Win32 application. So tkinter, Idle, turtle fail and the corresponding tests get skipped. 32 bit and 64 bit both work for me. Windows 7. -- https://mail.python.org/mailman/listinfo/python-list
Re: [RELEASED] Python 3.4.0 release candidate 1
On 2014-02-11 13:06, David Robinow wrote: On Tue, Feb 11, 2014 at 5:45 AM, Terry Reedy tjre...@udel.edu wrote: On 2/11/2014 5:13 AM, Terry Reedy wrote: ... I installed 64 bit 3.3.4 yesterday with no problem. I reran it today in repair mode and again, no problem. With 64 bit 3.4.0, I get There is a problem with this Windows Installer package. A program required for the install to complete could not be run. No, the generic message does not bother to say *which* program :-(. 34 bit 3.4.0 installed fine. I wrote too soon. Python 3.4.0rc1 (v3.4.0rc1:5e088cea8660, Feb 11 2014, 05:54:25) [MSC import tkinter Traceback ... import _tkinter ImportError: DLL load failed: %1 is not a valid Win32 application. So tkinter, Idle, turtle fail and the corresponding tests get skipped. 32 bit and 64 bit both work for me. Windows 7. Also works for me. Windows 8.1 64-bit. -- https://mail.python.org/mailman/listinfo/python-list
Re: [RELEASED] Python 3.4.0 release candidate 1
Terry Reedy tjre...@udel.edu wrote: On 2/11/2014 2:43 AM, Larry Hastings wrote: On behalf of the Python development team, I'm delighted to announce the first release candidate of Python 3.4. To download Python 3.4.0rc1 visit: http://www.python.org/download/releases/3.4.0/ I installed 64 bit 3.3.4 yesterday with no problem. I reran it today in repair mode and again, no problem. With 64 bit 3.4.0, I get There is a problem with this Windows Installer package. A program required for the install to complete could not be run. No, the generic message does not bother to say *which* program :-(. 34 bit 3.4.0 installed fine. I redownloaded 64bit 3.4.0 and install gives the same message. Can someone verify that this is not some bizarre glitch on my machine? I downloaded and installed it without problems on a 64bit Windows 7 system. Maybe it is a bizarre glitch on your system, or perhaps it assumes something is present which is there on my system and missing on yours. I see that part way through the install it downloads setuptools/pip from pypi. Did your system have network access? What happens if you enable the installer log by running: msiexec /i python-3.4.0rc1.amd64.msi /L*v logfile.txt Does it put any useful messages in logfile.txt? -- Duncan Booth -- https://mail.python.org/mailman/listinfo/python-list
Re: [RELEASED] Python 3.4.0 release candidate 1
On 2/11/2014 8:06 AM, David Robinow wrote: On Tue, Feb 11, 2014 at 5:45 AM, Terry Reedy tjre...@udel.edu wrote: On 2/11/2014 5:13 AM, Terry Reedy wrote: ... I installed 64 bit 3.3.4 yesterday with no problem. I reran it today in repair mode and again, no problem. With 64 bit 3.4.0, I get There is a problem with this Windows Installer package. A program required for the install to complete could not be run. No, the generic message does not bother to say *which* program :-(. 34 bit 3.4.0 installed fine. I wrote too soon. Python 3.4.0rc1 (v3.4.0rc1:5e088cea8660, Feb 11 2014, 05:54:25) [MSC import tkinter Traceback ... import _tkinter ImportError: DLL load failed: %1 is not a valid Win32 application. So tkinter, Idle, turtle fail and the corresponding tests get skipped. 32 bit and 64 bit both work for me. Windows 7. The failed 64-bit installs somehow messed up the 32-bit install. With 3.4 completely removed, including the residual directories, the 32-bit install works but the 64-bit install still gives me the same message. -- Terry Jan Reedy -- https://mail.python.org/mailman/listinfo/python-list
Re: [RELEASED] Python 3.4.0 release candidate 1
On 2/11/2014 10:42 AM, Duncan Booth wrote: Terry Reedy tjre...@udel.edu wrote: On 2/11/2014 2:43 AM, Larry Hastings wrote: On behalf of the Python development team, I'm delighted to announce the first release candidate of Python 3.4. To download Python 3.4.0rc1 visit: http://www.python.org/download/releases/3.4.0/ I installed 64 bit 3.3.4 yesterday with no problem. I reran it today in repair mode and again, no problem. With 64 bit 3.4.0, I get There is a problem with this Windows Installer package. A program required for the install to complete could not be run. No, the generic message does not bother to say *which* program :-(. 34 bit 3.4.0 installed fine. I redownloaded 64bit 3.4.0 and install gives the same message. Can someone verify that this is not some bizarre glitch on my machine? I downloaded and installed it without problems on a 64bit Windows 7 system. Maybe it is a bizarre glitch on your system, or perhaps it assumes something is present which is there on my system and missing on yours. As I noted in response to David, starting completely clean allows 32 bit version to install, but not 64 bit version. I see that part way through the install it downloads setuptools/pip from pypi. Did your system have network access? Enough to post the original message ;-). And yes, A box came up asking about that and I said yes. What happens if you enable the installer log by running: msiexec /i python-3.4.0rc1.amd64.msi /L*v logfile.txt A megabyte file with nearly 7000 lines Does it put any useful messages in logfile.txt? 'error' occurs on 40. most are like the following MSI (s) (40:08) [11:57:25:973]: Package to be registered: 'python-3.4.0rc1.amd64.msi' MSI (s) (40:08) [11:57:25:973]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (40:08) [11:57:25:973]: Note: 1: 2262 2: AdminProperties 3: -2147287038 Here is the one for the boxed message: Action 11:57:26: RemovePip. Action start 11:57:26: RemovePip. MSI (s) (40:0C) [11:57:26:426]: Note: 1: 1721 2: RemovePip 3: C:\Programs\Python34\python.exe 4: -m ensurepip._uninstall MSI (s) (40:0C) [11:57:26:426]: Note: 1: 2262 2: Error 3: -2147287038 Error 1721. 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. Action: RemovePip, location: C:\Programs\Python34\python.exe, command: -m ensurepip._uninstall MSI (s) (40:0C) [11:57:28:874]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (40:0C) [11:57:28:874]: Product: Python 3.4.0b2 (64-bit) -- Error 1721. 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. Action: RemovePip, location: C:\Programs\Python34\python.exe, command: -m ensurepip._uninstall MSI (c) (98:EC) [11:57:30:204]: PROPERTY CHANGE: Deleting SECONDSEQUENCE property. Its current value is '1'. Action ended 11:57:30: ExecuteAction. Return value 3. MSI (c) (98:EC) [11:57:30:204]: Doing action: FatalError A Can you make anything of these? -- Terry Jan Reedy -- https://mail.python.org/mailman/listinfo/python-list
Re: [RELEASED] Python 3.4.0 release candidate 1
Hi. On 11.2.2014. 17:21, Terry Reedy wrote: The failed 64-bit installs somehow messed up the 32-bit install. With 3.4 completely removed, including the residual directories, the 32-bit install works but the 64-bit install still gives me the same message. I had a similar problem with the beta 3 release where x64 failed to install on my computer. Not sure if the underlying issue is the same as yours but my issue was resolved after uninstalling the Visual Studio C++ runtime, rebooting and doing a clean install. I wanted to report the issue then, but since I could not reproduce it, I had nothing exact to say other than 'did not work for me, now it does, don't know if it was me or you'. :-) Hope this helps. Best regards, Jurko Gospodnetić -- https://mail.python.org/mailman/listinfo/python-list
[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) -- https://mail.python.org/mailman/listinfo/python-list
