-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
fix: check the activation script exists on Python virtual environments #29265
Conversation
💚 Build Succeeded
Expand to view the summary
Build stats
❕ Flaky test reportNo test was executed to be analysed. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
I directly got this merged to update the related PR's. @kuisathaverat This should also be forwardported to master I assume? |
#29265) (#29279) (cherry picked from commit 52e87f0) Co-authored-by: Ivan Fernandez Calvo <[email protected]>
#29265) (#29288) (cherry picked from commit 52e87f0) Co-authored-by: Ivan Fernandez Calvo <[email protected]>
What does this PR do?
It changes the way to check if the Python virtual environment is valid, not it check for the activation script instead of check only the existence of the folder.
Why is it important?
For some reason, the folder exists in the CI and it is empty, this forces to recreate it in case the activation script is not there.
Checklist
[ ] I have commented my code, particularly in hard-to-understand areas[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files[ ] I have added tests that prove my fix is effective or that my feature works[ ] I have added an entry inCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.