-
-
Notifications
You must be signed in to change notification settings - Fork 170
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
Revert "RFC3986 compatible URL.join honoring empty segments (#1039)" #1067
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1067 +/- ##
==========================================
- Coverage 62.60% 62.37% -0.24%
==========================================
Files 38 38
Lines 6721 6626 -95
Branches 368 356 -12
==========================================
- Hits 4208 4133 -75
+ Misses 2486 2466 -20
Partials 27 27
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
@@ -0,0 +1,3 @@ | |||
Reverted RFC3986 compatible URL.join honoring empty segments which was introduced in :issue:`1039`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bdraco FYI, Sphinx has a dedicated role :rfc:
which should be used to link RFCs. The rendered style would also be more consistent.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did discover that, and I changed it before I published it in the release step. At least I hope I did as my burnout level was pretty high at that point
This reverts commit e3dd736.
This change introduced a regression with parsing the query string in joined urls. #1066 attempted to fix the regression, but it became too involved. Since this doesn't look like there will be a quick fix, the change is being reverted so it can be tried again in the future.