Skip to content

Conversation

@charris
Copy link
Member

@charris charris commented Oct 14, 2025

Backport of #29885.

Not sure if there is any downsides to this, but I think this is much simpler and pretty much identical.
Plus, I don't quite like that the 1.25 factor could be large, although I admit it seems very unlikely (maybe impossible) to actually trigger a problem there.

EDIT: As a note, I have a similar function that caps overallocation and increments in "neat" values (which double as a minimum overallocation amount). I somewhat assumed that doesn't matter much, but we could definitely do either or both here as well.

Not sure if there is any downsides to this, but I think this is much
simpler and pretty much identical.
Plus, I don't quite like that the 1.25 factor could be large, although
I admit it seems very unlikely (maybe impossible) to actually trigger
a problem there.

Signed-off-by: Sebastian Berg <sebastianb@nvidia.com>
@charris charris added this to the 2.3.4 release milestone Oct 14, 2025
@charris charris added 03 - Maintenance 08 - Backport Used to tag backport PRs labels Oct 14, 2025
@charris charris merged commit 7583bed into numpy:maintenance/2.3.x Oct 14, 2025
74 of 75 checks passed
@charris charris deleted the backport-29885 branch October 14, 2025 17:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

03 - Maintenance 08 - Backport Used to tag backport PRs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants