| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Thanks @hugovk for the PR, and @ned-deily for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13. |
Sorry, something went wrong.
|
Thanks @hugovk for the PR, and @ned-deily for merging it 🌮🎉.. I'm working now to backport this PR to: 3.14. |
Sorry, something went wrong.
(cherry picked from commit 80ba4e1) Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
(cherry picked from commit 80ba4e1) Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
|
GH-144640 is a backport of this pull request to the 3.13 branch. |
Sorry, something went wrong.
|
GH-144641 is a backport of this pull request to the 3.14 branch. |
Sorry, something went wrong.
⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️Hi! The buildbot AMD64 Debian root 3.x (tier-1) has failed when building commit 80ba4e1. What do you need to do:
You can take a look at the buildbot page here: https://buildbot.python.org/#/builders/345/builds/13374 Summary of the results of the build (if available): == Click to see traceback logsTraceback (most recent call last):
File "/root/buildarea/3.x.angelico-debian-amd64/build/Lib/test/support/__init__.py", line 947, in gc_collect
gc.collect()
~~~~~~~~~~^^
ResourceWarning: unclosed file <_io.FileIO name=13 mode='wb' closefd=True>
|
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This PR adds --disable-pip-version-check to the pip invocation that upgrades certifi in Install Certificates.command, to avoid warnings like this:
Docs: https://pip.pypa.io/en/stable/cli/pip/#cmdoption-disable-pip-version-check
These sometimes show up on GitHub Actions as part of actions/setup-python, which I as an end user has little control over. And the funny thing is, that action had just upgraded pip right before calling Install Certificates.command. See python-pillow/Pillow#9424 (comment) for more details.
I think avoiding the warning in this script is okay. In normal use, the user double clicks the "Install Certificates.command" icon during installation, the default terminal upgrades certifi then terminates.
People will still see the warning later on regular pip invocations when they're in a normal terminal session, which is when they can actually do something about it.
(Let me know if this PR needs an issue or news.)