Steve Dower added the comment:
Updated the documentation and it should be in 3.5.0rc1's docs on using with
Windows.
--
resolution: - fixed
stage: - resolved
status: open - closed
___
Python tracker rep...@bugs.python.org
Changes by STINNER Victor victor.stin...@gmail.com:
--
components: +Windows
nosy: +paul.moore, tim.golden, zach.ware
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24640
___
New submission from Chris Krycho:
There is no `ensurepip` module bundled with the embedded distribution of Python
3.5 for Windows:
Z:\python-3.5.0b3-embed .\python -m ensurepip --upgrade
Z:\python-3.5.0b3-embed\python.exe: No module named ensurepip
This may be the *intent*, but I
Changes by STINNER Victor victor.stin...@gmail.com:
--
assignee: - docs@python
components: +Documentation
nosy: +docs@python
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24640
___
Steve Dower added the comment:
It's a deliberate exclusion, I just haven't gotten to all the documentation yet
(mostly because I still expect things to change).
My idea was that packages would be deployed statically alongside the embedded
distribution rather than going into a site-packages
Chris Krycho added the comment:
Using --root or --target (as appropriate to the specific package) does appear
to be the preferred approach for that, and given the constraints of an embedded
installation, I agree that that's the most reasonable solution. I spent a fair
bit of time reading up
