Re: Fixing #744145, `pip install --user --upgrade requests` breaks pip

On Wednesday, February 25, 2015 02:54:33 PM Thomas Kluyver wrote: > On 25 February 2015 at 14:40, Scott Kitterman wrote: > > Having re-read the bug, I don't see how this is anything other > > than user error in Debian. > > I hope you don't mean that installing any of the packages pip relies on >

Re: Fixing #744145, `pip install --user --upgrade requests` breaks pip

On Feb 25, 2015, at 05:40 PM, Scott Kitterman wrote: >I'm confused. Having re-read the bug, I don't see how this is anything other >than user error in Debian. As I read it, your proposed solution is directly >contradictory to what we wrote about .whil files in our Python policy: > > A v

Re: Fixing #744145, `pip install --user --upgrade requests` breaks pip

> On Feb 25, 2015, at 5:54 PM, Thomas Kluyver wrote: > > On 25 February 2015 at 14:40, Scott Kitterman > wrote: > Having re-read the bug, I don't see how this is anything other > than user error in Debian. > > I hope you don't mean that installing any of the packag

Re: Fixing #744145, `pip install --user --upgrade requests` breaks pip

On 25 February 2015 at 14:40, Scott Kitterman wrote: > Having re-read the bug, I don't see how this is anything other > than user error in Debian. > I hope you don't mean that installing any of the packages pip relies on under my home directory is 'user error'. The user shouldn't even need to kn

Re: Fixing #744145, `pip install --user --upgrade requests` breaks pip

On Wednesday, February 25, 2015 04:37:53 PM Barry Warsaw wrote: > Debian bug #744145 (Ubuntu LP: #1363642) describes this failure: > > $ pip install --user --upgrade requests > $ pip install --user --upgrade mistunes > > (well, any package will have the same effect for step #2) > > Quick recap:

Fixing #744145, `pip install --user --upgrade requests` breaks pip

Debian bug #744145 (Ubuntu LP: #1363642) describes this failure: $ pip install --user --upgrade requests $ pip install --user --upgrade mistunes (well, any package will have the same effect for step #2) Quick recap: upstream pip vendorizes (bundles) a bunch of its dependencies. This violates Deb

pyxs in Debian

Hi Maykel, I've just come across https://bugs.debian.org/692516 and was wondering what the current status is. It seems like the last round of mentoring/review was https://lists.debian.org/debian-python/2013/01/msg0.html and then things petered out (or went off list)? I'm not involved in Debia

Re: Build separate binary packages from single source

Brian May writes: > I just noticed https://pypi.python.org/pypi/devpi/ is just an empty > shell and useless by itself. That wasn't the case when this thread started, and I'm not happy to see it. It is apparently a deliberate response to the request for consistent versioning between all the comp

Re: Build separate binary packages from single source

[Ben Finney, 2015-02-25] > I'd still like to know how that should be done: package multiple Python > distributions from a single upstream tarball. just take a look at debian/rules example from my previous email -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl

Re: Request to join Python Modules Packaging Team

On Tue, 24 Feb 2015 23:46:31 +0100 Piotr Ożarowski wrote: > [Riley Baird, 2015-02-20] > > I would like to adopt the "slides" package as part of the Python > > Modules Packaging Team. Much of the work has already been done, and > > great! welcome :) Thanks for adding me! > > the only things left