[Python-Dev] [python-committers] [RELEASED] Python 3.4.0 release candidate 3 (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Mon Mar 10 14:17:57 CET 2014
- Previous message: [Python-Dev] [python-committers] [RELEASED] Python 3.4.0 release candidate 3
- Next message: [Python-Dev] Python 3.4 change in importlib/__init__.py breaking cxFreeze?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 10 Mar 2014 19:50, "Victor Stinner" <victor.stinner at gmail.com> wrote:
Hi, I tested Python 3.4rc3 installer on Windows: - all menu entries work (doc, doc server, help, IDLE, command line, etc.) - pip is installed, yeah! - my tracemalloc module works on Windows too ;-) - The uninstaller fully removes C:\Python34 The major Windows installer issues are fixed in the RC3.
Huzzah! :)
Note: As fully, I got a popup telling me that the MSI is untrusted, and I had to click on [OK] to confirm that I trust python.org.
I also tried to change pip version: I downgraded it from 1.5.4 to 1.5.3. In this case, C:\Python34 is not removed, I filled an issue for that, but it's maybe expected? http://bugs.python.org/issue20878
Yeah, that's expected - if pip is used to install extra packages, the uninstaller has historically left them alone. Changing the version of pip causes it to be treated like an independently installed package, so the uninstaller leaves it behind.
Cheers, Nick. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20140310/5302be15/attachment.html>
- Previous message: [Python-Dev] [python-committers] [RELEASED] Python 3.4.0 release candidate 3
- Next message: [Python-Dev] Python 3.4 change in importlib/__init__.py breaking cxFreeze?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]