Skip to content
This repository was archived by the owner on Aug 14, 2025. It is now read-only.

Conversation

@BenjaminRodenberg
Copy link
Member

Like discussed in #186 using pip3 will trigger a warning, if a recent pip version is used. However, #186 (comment) gives reasons to keep using pip3 (at least for a while). This PR adds comments in the code to point developers to the corresponding issue.

@BenjaminRodenberg BenjaminRodenberg self-assigned this Feb 27, 2020
@BenjaminRodenberg BenjaminRodenberg marked this pull request as ready for review February 27, 2020 10:13
@BenjaminRodenberg
Copy link
Member Author

@fsimonis do you think that the comments I added in the code are sufficient to help us bridging the time until python3/pip3 is truly the standard and python2/pip2 is truly dead? I would like to stick to using the more explicit calls to python3/pip3 until that point in time.

@fsimonis fsimonis removed their request for review August 14, 2025 11:32
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants