[issue19347] PEP 453 implementation tracking issue

2014-01-02 Thread Nick Coghlan
Nick Coghlan added the comment: Actually, with the docs update being the only remaining "this really should be done before 3.4 is released" issue related to PEP 453, I think this tracking issue has now served its purpose. So, closing this umbrella issue now, since issue 19407 covers the docs u

[issue19347] PEP 453 implementation tracking issue

2014-01-02 Thread Martin v . Löwis
Changes by Martin v. Löwis : -- priority: release blocker -> normal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue19347] PEP 453 implementation tracking issue

2014-01-02 Thread Nick Coghlan
Nick Coghlan added the comment: Agreed, it was mostly to ensure we reviewed the status to make sure we were happy with progress. The only remaining "must fix" item is the docs update, and that's shouldn't block beta 2 (although I'll still try to get at least an initial version done now that pip 1

[issue19347] PEP 453 implementation tracking issue

2014-01-02 Thread Martin v . Löwis
Martin v. Löwis added the comment: I propose to downgrade this from "release blocker" again. "prefer to have everything we can sorted" is IMO not a sufficient rationale to block the release; if taken literally, 3.4 could never ever release since it doesn't have everything sorted out that I wou

[issue19347] PEP 453 implementation tracking issue

2013-12-22 Thread Nick Coghlan
Nick Coghlan added the comment: Issue 20053 covers the fact that the default pip config file affects ensurepip and venv. -- ___ Python tracker ___ __

[issue19347] PEP 453 implementation tracking issue

2013-12-03 Thread Nick Coghlan
Nick Coghlan added the comment: Upgrading to release blocker status, since we'd prefer to have everything we can sorted before beta 2 -- nosy: +larry priority: normal -> release blocker ___ Python tracker

[issue19347] PEP 453 implementation tracking issue

2013-12-03 Thread Nick Coghlan
Nick Coghlan added the comment: Issue 19766 covers the fact that the vendored urllib3 needs to be updated in order to handle the case where Python is built without threading support. -- ___ Python tracker

[issue19347] PEP 453 implementation tracking issue

2013-11-24 Thread Nick Coghlan
Nick Coghlan added the comment: Issue 19734 covers the fact that pip environment variable settings impact venv and ensurepip -- ___ Python tracker ___ __

[issue19347] PEP 453 implementation tracking issue

2013-11-23 Thread Nick Coghlan
Nick Coghlan added the comment: Issue 19744 covers better handling of the case where SSL/TLS support is not available in the current Python. -- ___ Python tracker ___ __

[issue19347] PEP 453 implementation tracking issue

2013-11-22 Thread Nick Coghlan
Nick Coghlan added the comment: Created issue 19728 to track what is needed before the installation of pip can be made the default in the installers (at least for Windows, but I assume MvL's concerns would apply equally to the Mac OS X installer) -- ___

[issue19347] PEP 453 implementation tracking issue

2013-11-22 Thread Nick Coghlan
Nick Coghlan added the comment: Issue 19694 is a new issue for one of the buildbots objecting to the new venv tests. -- ___ Python tracker ___ __

[issue19347] PEP 453 implementation tracking issue

2013-11-22 Thread Nick Coghlan
Nick Coghlan added the comment: Issue 19693 covers an anomaly where "make altinstall && make install" doesn't quite do the same thing as "make install" (the "pip3" script will be missing in the former case) -- ___ Python tracker

[issue19347] PEP 453 implementation tracking issue

2013-11-11 Thread Nick Coghlan
Changes by Nick Coghlan : -- dependencies: +PEP 453: "make install" and "make altinstall" integration, PEP 453: Mac OS X installer integration, PEP 453: Windows installer integration, PEP 453: venv module and pyvenv integration -Compact int and float freelists, Potential overflows due

[issue19347] PEP 453 implementation tracking issue

2013-11-11 Thread Nick Coghlan
Nick Coghlan added the comment: New subtasks: Issue 19550: Windows installer integration Issue 19551: Mac OS X installer integration Issue 19552: venv module and pyvenv integration Issue 19553: "make install" and "make altinstall" integration open -- dependencies: +Compact int and flo

[issue19347] PEP 453 implementation tracking issue

2013-11-05 Thread Bohuslav "Slavek" Kabrda
Changes by Bohuslav "Slavek" Kabrda : -- nosy: +bkabrda ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue19347] PEP 453 implementation tracking issue

2013-10-26 Thread Nick Coghlan
Nick Coghlan added the comment: First two working issues created: Issue 19406 for the addition of ensurepip and its docs Issue 19407 for the Installing Python Modules updates -- dependencies: +PEP 453: add the ensurepip module, PEP 453: update the "Installing Python Modules" documentat

[issue19347] PEP 453 implementation tracking issue

2013-10-22 Thread Tshepang Lekhonkhobe
Changes by Tshepang Lekhonkhobe : -- nosy: +tshepang ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue19347] PEP 453 implementation tracking issue

2013-10-22 Thread Nick Coghlan
Nick Coghlan added the comment: Just clarifying how I plan to track this: as we start specific tasks, we'll create new issues and make this one depend on them. That seems better to me than creating a whole raft of issues up front that are then depending on each other. -- ___

[issue19347] PEP 453 implementation tracking issue

2013-10-22 Thread Nick Coghlan
Nick Coghlan added the comment: Check PEP 453 again: http://www.python.org/dev/peps/pep-0453/#changes-to-virtual-environments Rather than only changing pyvenv, the API in the PEP is to add "with_pip" parameters to the venv module API, so that anyone building pyvenv style tools on top of venv

[issue19347] PEP 453 implementation tracking issue

2013-10-22 Thread Vinay Sajip
Vinay Sajip added the comment: venv shouldn't need any changes. The pyvenvex.py [1] script I posted to distutils-sig installs setuptools and pip into venvs, and it can be used to update pyvenv (where AFAICT changes are only required to change where the pip to be installed comes from). [1] htt

[issue19347] PEP 453 implementation tracking issue

2013-10-22 Thread Nick Coghlan
Changes by Nick Coghlan : -- nosy: +dstufft, loewis, ned.deily, vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue19347] PEP 453 implementation tracking issue

2013-10-22 Thread Nick Coghlan
Nick Coghlan added the comment: One more task to track - updating to the latest upstream pip before beta 2. -- ___ Python tracker ___

[issue19347] PEP 453 implementation tracking issue

2013-10-22 Thread Nick Coghlan
New submission from Nick Coghlan: This is the overall tracking issue for the implementation of PEP 453. The following subtasks will be created as separate issues: - update the Installing Python Modules documentation to reference www.pip-installer.org in Python 2.7, 3.3 and 3.4 (ncoghlan) - ini