[PR #7819/dfc3f899 backport][3.9] Skip filtering CookieJar
when the jar is empty or all cookies have expired
#7822
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a backport of PR #7819 as merged into master (dfc3f89).
What do these changes do?
The filtering itself and its preparation in
CookieJar.filter_cookies()
is expensive. Sometimes there are no cookies in the jar or all cookies have expired. Skip filtering and its preparation in this case.Because the empty check is much cheaper than
_do_expiration()
, I think it deserves to be duplicated before and after calling_do_expiration()
.Are there changes in behavior for the user?
No.
Related issue number
#7583 (comment)
Checklist
CONTRIBUTORS.txt
CHANGES
folder<issue_id>.<type>
for example (588.bugfix)issue_id
change it to the pr id after creating the pr.feature
: Signifying a new feature..bugfix
: Signifying a bug fix..doc
: Signifying a documentation improvement..removal
: Signifying a deprecation or removal of public API..misc
: A ticket has been closed, but it is not of interest to users.