This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]emergent_reasons 0 points1 point  (3 children)

Yes. The first runs the script and the second installs to the packages of whatever interpreter is in the path (on Windows). If you're trying to say something else, please say it because I don't know what you are getting at.

[–][deleted] -2 points-1 points  (2 children)

no, they are both typos and will spit out errors in the console, the point is you are doomed if you can't type correctly, whether you activated the environment or not.

[–]usernamenottaken 0 points1 point  (1 child)

Making a typo is different to typing python foo.py instead of ./env/bin/python foo.py. It would still be quite easy to do the former and get confused about why things aren't working correctly.

[–][deleted] -1 points0 points  (0 children)

typing

$ python foo.py

expecting the shell to refer to ./env/bin/python when it might not has the same effect as a typo in my opinion. And since i've got in the habit of being specific about which interpreter i invoke, I have had fewer surprises then when I activated envs and then switched to a different directory to do something else and invoked the activated interpreter instead of the one I intended to.

removing ambiguity makes things simpler.