-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Switch to using yarl.URL.absolute
over yarl.URL.is_absolute()
#9171
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
Conversation
.absolute is directly cached and preferred
~yarl.URL.absolute
over URL.is_absolute()
yarl.URL.absolute
over yarl.URL.is_absolute()
not backported to 3.10 since the minimum yarl requirement is too old there |
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## master #9171 +/- ##
=======================================
Coverage 98.31% 98.31%
=======================================
Files 107 107
Lines 34483 34483
Branches 4093 4093
=======================================
Hits 33901 33901
Misses 411 411
Partials 171 171
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Backport to 3.11: 💚 backport PR created✅ Backport PR branch: Backported as #9185 🤖 @patchback |
) (cherry picked from commit 0462ae6)
…` over `yarl.URL.is_absolute()` (#9185) Co-authored-by: J. Nick Koston <[email protected]>
Backport to 3.10: 💚 backport PR created✅ Backport PR branch: Backported as #9291 🤖 @patchback |
) (cherry picked from commit 0462ae6)
…` over `yarl.URL.is_absolute()` (#9291) Co-authored-by: J. Nick Koston <[email protected]>
What do these changes do?
.absolute
is directly cached and preferredAre there changes in behavior for the user?
no
Is it a substantial burden for the maintainers to support this?
no
related issue #2779