Skip to content

updated pip command for python3 #61

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

updated pip command for python3 #61

wants to merge 2 commits into from

Conversation

kskeshav
Copy link

No description provided.

@YannickJadoul
Copy link

As far as I'm concerned, it's up to the user to make sure pip refers to the correct installation of Python. pip vs. pip3 is merely a Debian repositories convention, I believe. On my system:

$ pip --version
pip 20.2.2 from /home/yannick/.local/lib/python3.6/site-packages/pip (python 3.6)

@henryiii
Copy link
Collaborator

henryiii commented Oct 2, 2020

Personally, I'd generally recommend python -m pip always (or python3 -m pip, perhaps, but not explicitly both); there are too many possible bugs with using pip directly. Most recent example I can think of: scikit-hep/particle#269

I like the MSVC 2015 "or newer" change, though.

@henryiii
Copy link
Collaborator

Can't edit this to just keep the "or higher" wording, so closing.

@henryiii henryiii closed this Apr 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants