Version 0.24 #2534
Replies: 5 comments 3 replies
-
What's the expected release date for 0.24? This will stop dependabot from trying to push an update which causes a dependency conflict with |
Beta Was this translation helpful? Give feedback.
-
Please release that version ASAP. Thanks. |
Beta Was this translation helpful? Give feedback.
-
@tomchristie Can you please have a look at this? Thanks |
Beta Was this translation helpful? Give feedback.
-
@tomchristie, @madkinsz: Is there any blocker for a 0.24 release? Is there anything we can help? |
Beta Was this translation helpful? Give feedback.
-
I guess we'll see a new release in the next few hours: #2652 Thanks team! |
Beta Was this translation helpful? Give feedback.
-
We've got a few upcoming behavioural changes, that I think we ought to push on with now.
This will commit us to our next release being version 0.24.
Here's what I think we'd like to
Fix
iter_lines()
to match the behaviour ofsplitlines()
. No trailing newlines on strings.Pull request Change LineDecoder to match stdlib splitlines, resulting in significant speed up #2423
Would close LineDecoder is accidentally quadratic: iter_lines() seems to hang forever #2422.
Add explicit
NetRCAuth()
class instead of built-in client behaviour.Pull request Add
NetRCAuth()
class. #2535Would close NetRCInfo.netrc_info() doesn't work when run in a systemd service with DynamicUser=true #2532.
Would close follow_redirects and. edit: no, it wouldn't.netrc
credentials #2088Remove our
rfc3986
dependancy.Pull request Drop
rfc3986
requirement. #2252.Would close Some URLs with unescaped query strings cannot resolve relative redirects. #1833
Would close RFE: provide suport for
rfc3986
2.0.0 #2169.Prefer
%20
over+
for spaces in query parameters.Brings us more in line with browser behaviours.
Pull request Use '%20' for encoding spaces in query parameters. #2543.
Would close Use percent encoding for spaces in query parameters #2536.
See discussion Encode spaces in query parameter with %20 instead of + #2460.
Improve logging, adding
httpcore
logging, and switching to a more standard config style.Pull request Use standard logging style #2547
Pull request Add
DEBUG
level logging. httpcore#648Would close Review logging. #2042.
I also intend to raise a discussion around making
idna
support be opt-in, rather than on-by-default, which might or might not be worth aiming at 0.24.Are we all good with pushing on with getting a 0.24 release on track?
Beta Was this translation helpful? Give feedback.
All reactions