Skip to content

pip raises powershell exception on failed environment markers #4826

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
ghost opened this issue Oct 31, 2017 · 4 comments
Closed

pip raises powershell exception on failed environment markers #4826

ghost opened this issue Oct 31, 2017 · 4 comments

Comments

@ghost
Copy link

ghost commented Oct 31, 2017

  • Pip version: 9
  • Python version: 3.6
  • Operating system: windows

Description:

I attempted to install a github project, and pip failed the powershell command.

What I've run:

See https://ci.appveyor.com/project/xianyi/openblas/build/0.2.19.764/job/3qcu77o16ctq319j

Command executed with exception:   Ignoring typing: markers 'python_version < "3.5"' don't match your environment

pip should not have failed the build. It should have ignored typing and continued.

@ghost ghost changed the title pip : Ignoring typing: markers 'python_version < "3.5"' don't match your environment pip raises powershell exception on failed environment markers Oct 31, 2017
@benoit-pierre
Copy link
Member

I think the issue is with AppVeyor marking the command as failed because of output on stderr, it works fine with pip install -q: https://ci.appveyor.com/project/benoit-pierre/openblas/build/job/1jugjvg7sajb86sv

Also, doesn't this particular command belong to the install section?

@ghost
Copy link
Author

ghost commented Oct 31, 2017

The appveyor sections don't matter. It's wherever you feel like putting them.

@ghost
Copy link
Author

ghost commented Oct 31, 2017

Closing; will use -q from now on.

@ghost ghost closed this as completed Oct 31, 2017
@benoit-pierre
Copy link
Member

Alternatively, don't use powershell if the command will write to stderr: https://help.appveyor.com/discussions/problems/5413-calling-external-executable-causes-nativecommanderror-despite-no-apparent-error

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 15, 2021
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant