-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Apply tls_verify and tls_cacerts config to ImageDownloader (#11715) #11716
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
Apply tls_verify and tls_cacerts config to ImageDownloader (#11715) #11716
Conversation
c5c32c1 to
5d69b5f
Compare
|
If possible, can you check where other |
I looked around to see if there were any more obvious cases at first but will double check. Good idea. Ok: $ git grep 'from sphinx.util import' | grep requests
sphinx/builders/linkcheck.py:from sphinx.util import encode_uri, logging, requests
sphinx/ext/intersphinx.py:from sphinx.util import logging, requests
sphinx/transforms/post_transforms/images.py:from sphinx.util import logging, requests
tests/test_build_linkcheck.py:from sphinx.util import requestsThe 3 clients of the requests util here are:
So I think we're good! |
|
Good then! Could you add a CHANGES entry please? @AA-Turner I think we're good unless you want to wrap small PRs for the day when 7.3.0 is planned to be released. |
bd3af9e to
0c72934
Compare
Done! |
|
Perfect! In the future, if you want to contribute again, don't force push commits since it makes incremental review harder (we squash them at the end anyway). |
Ok sorry. The 2nd commit on the followup had the wrong email address, so I only force pushed an update to the email to that one commit, hoping the tooling would show just that, but I see what you're saying, and can understand that. |
# Conflicts: # CHANGES.rst
Subject: Apply tls_verify and tls_cacerts config to ImageDownloader
Feature or Bugfix
Purpose
Detail
Relates