** Bug watch added: github.com/pypa/pip/issues #1668
https://github.com/pypa/pip/issues/1668
** Changed in: pip
Importance: Undecided => Unknown
** Changed in: pip
Status: New => Unknown
** Changed in: pip
Remote watch: None => github.com/pypa/pip/issues #1668
--
You received
** Changed in: python-pip (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1419695
Title:
Should default to --user to not fail default pip install usage
To
Well, the debian bug was about this, and you commented there telling to
hold on as upstream/you was working on it and going to ship something. I
didn't want at the time putting pressure with a firm date for ubuntu,
thinking that would be shipped way in advance upstream.
I understand that the
We're unlikely to ship a solution within a week, however we can likely
hammer out what solution we're going to go with and probably land
something in trunk so that Ubuntu isn't different/broken it's just ahead
of the curve.
I wish y'all had reached out to us so we could have prioritized the
Speaking as a pip core developer, please revert this and wait for us to
fix it.
As I mentioned in a similar bug for Debian (https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=725848) jumping ahead of upstream on this is going
to make things WAY worse for a lot of people. You're using a custom
I'm also concerned about getting ahead of Debian here. While I
understand release cycle skew (e.g. Jessie is still in freeze), I think
this will make it more difficult to merge later and remove the delta.
If we don't do that, then there will be even more confusing user
experience between
This bug was fixed in the package python-pip - 1.5.6-4ubuntu1
---
python-pip (1.5.6-4ubuntu1) vivid; urgency=medium
* add debian/patches/set_user_default.patch,
debian/pip-manpage.rst: (LP: #1419695)
Default to --user on non virtualenv setup to ensure that
default pip
Sorry, shift+Enter
I'm opened to any real proposal, compatible with the vivid feature freeze
timeframe.
Other way to deal with it:
- pip install without the right perm to write to /usr/local, instead of getting
the not-so-great traceback it's writing at the moment, would redirect to a wiki
We are trying to get the same behavior between multiple package system
installation here (ruby, npm, pip…). All the others have the sane use
default.
When we started to write about it, the Debian bug was in discussion and
opened and I saw that you discussed that it was in progress upstream.
** Bug watch added: Debian Bug tracker #725848
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725848
** Also affects: pip (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725848
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
FYI: pip upstream bug (couldn't link github bug in launchpad):
https://github.com/pypa/pip/issues/1668
** Also affects: pip
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: pip (Debian)
Status: Unknown = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1419695
Title:
Should default to --user to not fail default pip install usage
To manage
** Branch linked: lp:ubuntu/vivid-proposed/python-pip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1419695
Title:
Should default to --user to not fail default pip install usage
To manage
** Package changed: pip (Ubuntu) = python-pip (Ubuntu)
** Package changed: pip (Debian) = python-pip (Debian)
** Changed in: python-pip (Ubuntu)
Status: New = Fix Committed
** Changed in: python-pip (Ubuntu)
Assignee: (unassigned) = Didier Roche (didrocks)
--
You received this bug
14 matches
Mail list logo
