![]() WARNING: this package provides a script called "virtualenv", and I put this (This would be a reasonable first fix for someone new to pip - does pip's issue tracker have a tag for those?) (Or heck, it could even suggest they run pip fix-user-path to have pip automatically add tihs to their ~/.profile - it's a little wonky but not too hard to make reasonably robust, and if it's a manual action that tells the user what it's doing as it runs then it should be reasonable helpful.) When pip install -user installs a script into ~/.local/bin (or the equivalent on other OSes, why not), then it should check the current os.environ, and if this directory is not on the PATH, then it should print an explanatory message that warns the user and gives them some information on how to fix the problem. But, even once the fix lands, all it will do is change the default for newly created accounts - so for a long time, there are going to be people who try running pip install -user and end up with it dropping executables into a directory that's not on $PATH. This is hopefully on its way to being fixed ( bash 4.3-15 is on its way into Debian unstable now, and should hopefully land in Debian testing in a few weeks, bug report here the Ubuntu bug that will hopefully be used to justify a backport of this fix into Xenial is here). ![]() Historically, this directory has not been on the default Debian/Ubuntu $PATH.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |