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.

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

Setting PIP options can break environment setup #942

Closed
henryiii opened this issue Nov 28, 2021 · 2 comments · Fixed by #956
Closed

Setting PIP options can break environment setup #942

henryiii opened this issue Nov 28, 2021 · 2 comments · Fixed by #956

Comments

@henryiii
Copy link
Contributor

henryiii commented Nov 28, 2021

Description

Setting a pip option, like PIP_USE_DEPRECATED=out-of-tree-build can break the initial setup, because this option gets applied to the original pip version (21.1 on Windows) instead of our pinned version. We should possibly ignore PIP_* variables or all environment variables during this initial setup for the pinned versions of things.

See pybind/cmake_example#66

Example of problematic line:

Build log

https://github.com/pybind/cmake_example/runs/4346290813?check_suite_focus=true

CI config

https://github.com/pybind/cmake_example/blob/c06fc016af76bd0f6a637705afc5d4cbfa554f5a/.github/workflows/wheels.yml#L49

@joerick
Copy link
Contributor

joerick commented Nov 29, 2021

Hmm yes, I can see the argument. We could also defer applying CIBW_ENVIRONMENT until after our internal tools install? Not sure which is preferable though.

@henryiii
Copy link
Contributor Author

henryiii commented Dec 1, 2021

It would be simpler to defer till after the internal tools install, since we set a few pip variables (like the version check).

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 a pull request may close this issue.

2 participants