| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
…et_proxy_response_headers`
|
Friendly ping :) |
Sorry, something went wrong.
|
@JelleZijlstra @AlexWaygood we have a little time left :) |
Sorry, something went wrong.
There was a problem hiding this comment.
Does seem like None makes more sense here, but I'd prefer to get @gpshead's opinion.
As an aside it's amusing this test is still called test_httplib, after the Python 2 name of this module.
Sorry, something went wrong.
|
None feels awkward because you are then forced to check the return value before you use it rather than just blindly use a .get("field") style API. Your goal seems to be to keep the type annotation signature simple. Can we instead return an empty HTTPMessage class? |
Sorry, something went wrong.
|
I marked this as a release blocker to force us to decide before 3.12rc1 so that we don't wind up with our new API needing to have a deprecation cycle and behavior change in the future (or just live with what is understandably perceived as an API wart). |
Sorry, something went wrong.
|
@gpshead yes, from this side empty HTTPMessage might seem better. Questions:
|
Sorry, something went wrong.
honestly... that idiom may be enough, I expect this is going to be a very rarely used API. |
Sorry, something went wrong.
|
Thanks everyone :) |
Sorry, something went wrong.
…et_proxy_response_headers` (pythonGH-105628) (cherry picked from commit 490295d) Co-authored-by: Nikita Sobolev <mail@sobolevn.me>
|
GH-106738 is a backport of this pull request to the 3.12 branch. |
Sorry, something went wrong.
…et_proxy_response_headers` (python#105628)
| Back | FazBrowse Home | New Git URL |
See #104248 (comment)
CC @nametkin
📚 Documentation preview 📚: https://cpython-previews--105628.org.readthedocs.build/