[issue19550] PEP 453: Windows installer integration

Nick Coghlan added the comment: I think "Off by default" is a reasonable solution for the beta (and even 3.4 final), but a separate issue explaining *why* it's off by default would be good. I can then ping the pip folks to ask for suggestions - if they come up with something workable, we may be a

[issue19550] PEP 453: Windows installer integration

Ned Deily added the comment: If it is acceptable for the "Remove" option to be somewhat unpredictable in the case where pip or setuptools was already installed and not by the installer, would "python -m pip uninstall --yes pip setuptools" work? If not, should a new issue be opened to find a s

[issue19550] PEP 453: Windows installer integration

Nick Coghlan added the comment: That sounds reasonable to me - thanks! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue19550] PEP 453: Windows installer integration

Martin v. Löwis added the comment: I have now committed the changes to the installer. A demo installer can be found at http://prof.beuth-hochschule.de/fileadmin/user/mvon_loewis/python-3.4.16027.msi I'm skeptical about the lack of proper deinstallation: per convention, uninstallation of softw

[issue19550] PEP 453: Windows installer integration

Roundup Robot added the comment: New changeset e0c4a5b2b739 by Martin v. Löwis in branch 'default': Issue #19550: Implement Windows installer changes of PEP 453 (ensurepip). http://hg.python.org/cpython/rev/e0c4a5b2b739 -- nosy: +python-dev ___ Python

[issue19550] PEP 453: Windows installer integration

Nick Coghlan added the comment: After a CPython installation with the option checked, the installed pip should be at least as recent as the bundled one: http://www.python.org/dev/peps/pep-0453/#invocation-from-the-cpython-installers You're right the prompt may be better as something like "Instal

[issue19550] PEP 453: Windows installer integration

Martin v. Löwis added the comment: I'm currently blocked on a discrepancy of this request and PEP 453. You are asking me to run "ensurepip --upgrade", whereas the PEP asks for an option to install the bundled pip (i.e. a mere ensurepip). Which of these should be done? --

[issue19550] PEP 453: Windows installer integration

Martin v. Löwis added the comment: I missed the original message. I'll try to come up with a patch. -- ___ Python tracker ___ ___ Pyth

[issue19550] PEP 453: Windows installer integration

Martin v. Löwis added the comment: IIUC, the current implementation strategy is to check the wheels into source control. If so, what's to be done in the installer (except for making sure that the wheels get bundled and installed into the msi, which it should do by default?) -- __

[issue19550] PEP 453: Windows installer integration

Changes by Nick Coghlan : -- stage: -> needs patch type: -> enhancement ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue19550] PEP 453: Windows installer integration

New submission from Nick Coghlan: Part of the PEP 453 implementation as tracked in issue 19347. This issue covers the Windows installer updates: * new option to choose whether or not to invoke "python -m ensurepip --upgrade" on the just installed Python * also add the result of calling 'sysco

[issue19550] PEP 453: Windows installer integration

Changes by Nick Coghlan : -- dependencies: +PEP 453: add the ensurepip module ___ Python tracker ___ ___ Python-bugs-list mailing list