Comment 3 for bug 1419695

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 flag that's only going to exist in versions of pip that comes from Ubuntu's archive. This means that behavior is going to change drastically if end users switch between systems or upgrade (or downgrade!) or even just reinstall their pip through pip itself. This is going to confuse people, it's going to break lots of tools like salt, puppet, chef, etc.

Changing this is a massively incompatible change that needs to be done carefully and with a lot of thought about how best to do it without causing a lot of negative impact for pip's users. Going off on your own is only going to make a bad situation (Python packaging) that we're slowly trying to make better a lot more confusing and a lot worse.