MAINT: f2py: Stop setting re._MAXCACHE to 50.#31105
Merged
Merged
Conversation
The value has been set to 50 for more than 20 years. Computers generally have much more memory now than they did 20 years ago, so we should be able to let `re` use the default. Closes numpygh-31104.
Contributor
|
That seems obviously correct at this point indeed. |
Member
|
Thanks @WarrenWeckesser. The docs build CI could not find the scipy intersphinx reference. Hopefully that is a once-off failure. |
Member
|
I tagged this for backport, seems pretty safe. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
The value has been set to 50 for more than 20 years. Computers generally have much more memory now than they did 20 years ago, so we should be able to let
reuse the default.Closes gh-31104.
AI Disclosure
No AI tools used.