[issue24640] no ensurepip in embedded Windows distribution

2015-08-11 Thread Steve Dower

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
http://bugs.python.org/issue24640
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue24640] no ensurepip in embedded Windows distribution

2015-07-15 Thread STINNER Victor

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
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue24640] no ensurepip in embedded Windows distribution

2015-07-15 Thread Chris Krycho

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 haven't been able to find any documentation to 
that effect in the [docs](https://docs.python.org/3.5/library/ensurepip.html). 
It looks like it should either be included with the distribution or noted as 
excluded in the docs. (I can readily submit a patch to the latter if it needs 
doing.)

(Background: I'm looking at various ways to bundle up and ship a Python 
application, and as part of that am looking at just shipping the embedded 
Python distribution, which may end up being the most straightforward for us. 
One of the things I'm still sorting out is the best to get and bundle up 
dependencies if that's the approach we take.)

--
components: Installation
messages: 246775
nosy: chriskrycho, dstufft, ncoghlan, steve.dower
priority: normal
severity: normal
status: open
title: no ensurepip in embedded Windows distribution
type: behavior
versions: Python 3.5

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24640
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue24640] no ensurepip in embedded Windows distribution

2015-07-15 Thread STINNER Victor

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
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue24640] no ensurepip in embedded Windows distribution

2015-07-15 Thread Steve Dower

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 directory (which should 
also be missing). Obviously this needs to be written up, but it may not be 
reasonable.

To automate packaging you probably want to use a separate pip to install into a 
temporary directory (--root option? I forget the option right now) and bundle 
that up. Does that sound feasible for you?

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24640
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue24640] no ensurepip in embedded Windows distribution

2015-07-15 Thread Chris Krycho

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 on that and the other options, and can't see a better 
one. I've already verified that approach will work for us, so I imagine it 
should for others as well.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24640
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com