-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
'This environment is externally managed' python error #8615
Comments
Hello @TheMostDiligent , We will take a look |
After some digging I figured that this happens because python was updated to version 12 and it changed how packages are installed. How do I solve "error: externally-managed-environment" every time I use pip 3? I don't think there is anything that can be done on the runner side, so I am closing this issue. |
Homebrew wants you to create a virtual env so that pip-installed modules don’t break something in your system. Same is true if working with python installed by apt-get in Ubuntu for same reason. |
Question is whether the marker file should be present at all in this context, see: |
Description
In MacOS-12 runner version 20231017.6, CMake configuration steps in our CI builds started to fail with the following error:
Platforms affected
Runner images affected
Image version and build link
Failing runner:
OK runner:
Is it regression?
Yes, 20231017.6. Worked OK in 20230921.4
Expected behavior
CMake configuration completes successfully, as it used to.
Actual behavior
CMake configuration fails.
Repro steps
For us the build fails on this commit: DiligentGraphics/DiligentFX@d544c7c
The text was updated successfully, but these errors were encountered: