why python -m pip? (beginner - intermediate) anthony explains #103

today I talk about how it's easy to get confused when installing packages and how to fix that with a different command! (as well as fun times on windows)

==========

I won't ask for subscriptions / likes / comments in videos but it really helps the channel. If you have any suggestions or things you'd like to see please comment below!

[erwan]

The main reason why I use `python -m pip` is in another video:
Shebang length is limited and `pip install` may unexpectedly fail with a not so easy to debug error, for instance by renaming a Jenkins job:

Thanks for covering everything!

[mfeickert]

This is great! I've tried my best to advocate for python -m pip over the last few years, but I didn't know about the Windows issue until now. Thanks for sharing another important motivation for this!

[burnere]

How do you make your (reasonably) smooth transitions between guest and host OS? And how do you maintain Ubuntu in full-screen when running CMD in the foreground?

[tombraril]

Thanks, sir for this wonderful video. But, I do have a question. How do windows users having both Python 3 and Python 2 install a package for just Python 3 only or Python 2 only as you did in your Linux distro or Mac terminal? Thanks and waiting in anticipation for your response.

[UriYakir]

Hey, kind of a stupid question but I was wondering - in my experience I’ve noticed that all python installation come with one interpreter executable: “python.exe”. This makes it very confusing when dealing with multiple python versions. What I usually do is copy the interpreter file and rename it with a more significant name, e.g: “python37”. Then I can use that name when running python files via cmd. Is this the usual way of doing it? Or is there a better way?