On Fri, Nov 6, 2015 at 4:52 AM, Glyph Lefkowitz <gl...@twistedmatrix.com> wrote: > > Rather than trying to figure out what the "right" way for users to invoke > `pip´ to begin with is, why not just have Pip start providing more > *information* about potential problems when you invoke it? > > If you invoke 'pip[X.Y]' and it matches 'python -m pip' in your current > virtualenv, don't say anything; similarly if you invoke 'python -m pip' and > 'which pip' matches. But if there's a mismatch, pip can print information > in both cases. This would go a long way to alleviating the confusion that > occurs when users back themselves into one of these corners, and would > alert users to potential issues before they become a problem; right now you > have to be a dogged investigative journalist to figure out why pip is doing > the wrong thing in some cases. >
I like this solution which is easy to implement and should directly help the user without any deprecation process.
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
