Re: Python 3.4 and ensurepip (rehashed, long)
----- Original Message -----
> On Mar 21, 2014, at 04:30 AM, Bohuslav Kabrda wrote:
> I'd still like something like that. On Debian, Python adds a /usr/local
> directory to sys.path, but it's not /usr/local/lib/pythonX.Y/site-packages,
> it's .../dist-packages for reasons we've long hashed out and I don't want to
> re-open. Suffice to say that we do have a directory where `sudo pip install`
> could install to that would play nice with system Python but wouldn't
> interfere with distro packages. While I don't much like `sudo pip install`
> as
> a general recommendation, in principle we support that.
So it seems that we should really concentrate this discussion. On Fedora's python-devel, Nick said that he'd like to hack up adding more load paths at PyCon next month and in this thread Donald said that he has an idea for PEP for that. We, as Fedora Python and pip maintainers would love to see something like that and Debian already has a version of it downstream. This really starts to look like we should all join one mailing list and discuss this in one thread :)
What about the pypa ML? I guess joining one more ML is worth this...
> Just to keep in mind when proposing this upstream that distros will have
> similar goals, but different concrete paths.
>
> >> What will rewheeling prefer when:
> >>
> >> * bundled ones are newer than system ones?
> >
> >That's not currently implemented in our patch, since we'll be removing
> >bundled wheels and relying on system versions only. But to solve this
> >situation for the upstream patch, we'll do it like this
> >- if user runs just "python3 -m ensurepip", nothing will happen
> >- if user runs "python3 -m ensurepip --upgrade", his setuptools/pip will get
> >upgraded
> >Note, that this corresponds with current ensurepip documentation [2] of such
> >situations.
>
> I read the patch, and I think I get it, but just to be clear, rewheeling
> only covers pip and setuptools, not arbitrary other packages, right?
rewheel should be able to create a wheel from arbitrary package, although there are some known issues that we're still trying to figure out. It is true that we'd also need to explictly rewheel all pip's dependencies in the patch for ensurepip and that part of the patch would remain downstream only, since upstream would use bundled pip with bundled requests etc.
> Cheers,
> -Barry
--
Regards,
Slavek.
Reply to: