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
Breaking drop of URL.raw in patch release 0.23.1 #2462
Comments
Looks like this has been raised in #2457 but it seems like reverting here would be more ideal (and safer) than hoping other dependencies all refactor their usage? |
@developerDemetri - Would it help you folks if we released a patch version which included |
Yup, that should help for our use case and anyone else relying on |
This made a backward-incompatible change, removing the attribute URL.raw. It looks like the maintainers plan to reinstate it as a namedtuple in a coming patch release. encode/httpx#2462
This made a backward-incompatible change, removing the attribute URL.raw. It looks like the maintainers plan to reinstate it as a namedtuple in a coming patch release. encode/httpx#2462
@tomchristie I took a stab at this in #2481 |
Both 0.23.1 [1] and 0.23.2 [2] come with backward-incompatible changes, both of which are (partially) reverted later. Pushing to [community-testing] first as I'm scared. [1] encode/httpx#2462 [2] encode/httpx#2538 git-svn-id: file:///srv/repos/svn-community/svn@1378295 9fca08f4-af9d-4005-b8df-a31f2cc04f65
Both 0.23.1 [1] and 0.23.2 [2] come with backward-incompatible changes, both of which are (partially) reverted later. Pushing to [community-testing] first as I'm scared. [1] encode/httpx#2462 [2] encode/httpx#2538 git-svn-id: file:///srv/repos/svn-community/svn@1378295 9fca08f4-af9d-4005-b8df-a31f2cc04f65
The patch release
0.23.1
included a breaking change in #2241The justification seems to be that "we don't use it", but
url.raw
is a public property used by other libraries includingddtrace
0.x versions: https://github.com/DataDog/dd-trace-py/blob/v0.61.3/ddtrace/contrib/httpx/patch.py#L41Can this breaking change be reverted and maybe soft-deprecated? @tomchristie @michaeloliverx
The text was updated successfully, but these errors were encountered: