[issue20071] What should happen if someone runs ./python -m ensurepip in the build environment?

2014-09-08 Thread Ned Deily
Changes by Ned Deily n...@acm.org: -- nosy: +dstufft, ncoghlan, ned.deily versions: +Python 2.7, Python 3.4, Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20071 ___

[issue20071] What should happen if someone runs ./python -m ensurepip in the build environment?

2014-09-08 Thread Nick Coghlan
Nick Coghlan added the comment: The whole sys.path initialisation scheme is pretty broken when running from a source checkout, so the short answer is it won't work, and it isn't really fixable in a maintenance release. System Python 3: sys.path = [ '/home/ncoghlan/devel/py3k',

[issue20071] What should happen if someone runs ./python -m ensurepip in the build environment?

2014-09-08 Thread Nick Coghlan
Nick Coghlan added the comment: Note that if I find time to implement the startup sequence redesign for PEP 432/issue #22257 (which is finally starting to look like it may actually happen some time in the next few months), a proper fix may end up being possible for 3.5. We shouldn't bet on

[issue20071] What should happen if someone runs ./python -m ensurepip in the build environment?

2013-12-26 Thread R. David Murray
New submission from R. David Murray: Someone on IRC reported doing this, and it (logically enough) gave a permission error trying to install into /opt. That may be exactly what it should do...but if he'd done it as root, presumably it would have tried to install PIP without python having