Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Consider switching to "python -m pip" in examples #107

Open
ncoghlan opened this issue Oct 5, 2014 · 1 comment
Open

Consider switching to "python -m pip" in examples #107

ncoghlan opened this issue Oct 5, 2014 · 1 comment

Comments

@ncoghlan
Copy link
Member

ncoghlan commented Oct 5, 2014

The bare "pip" invocation can fail in various circumstances, and it isn't clear how to invoke it such that it applies to the expected version of Python when multiple versions are installed in parallel. "python -m pip" works in more cases, and works cleanly with version switching invocations, like the Python Launcher for Windows, and python vs python3 at the system level on *nix systems.

http://bugs.python.org/issue21699 covers a new bug discovered with running pip from Windows directories containing spaces in Python 3.4
@illume
Copy link
Contributor

illume commented Feb 23, 2015

The pip bug you mention caused by distlib is fixed: https://bitbucket.org/pypa/distlib/issue/47

"various circumstances" is vague, and is not convincing.

Who updated the python docs to suggest python -m pip? It's just confusing telling people to do things in all sorts of different ways.

The pip guide does not suggest using this method.

No one uses this in practice.

python -m also fails for old python versions. Python 2.6, 2.7, 3.x all have different -m behaviour.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@illume @ncoghlan