Skip to content

BUG: fix casting issue in center, ljust, rjust, and zfill #29369

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

Merged
merged 1 commit into from
Jul 14, 2025

Conversation

ngoldbaum
Copy link
Member

Fixes #29359.

We were comparing signed and unsigned integers so any negative width wasn't being corrected.

Copy link
Member

@seberg seberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Func casting, but I think we said it may not be worthwhile to deal with such overflows on 32bits (indexing is also slightly sloppy with unsigned and nobody ever notices).

Negative values seem almost error worthy, but so long it is supported in the Python version, this seems good.

@seberg seberg merged commit 8b43d86 into numpy:main Jul 14, 2025
77 checks passed
@seberg seberg added the 09 - Backport-Candidate PRs tagged should be backported label Jul 14, 2025
charris pushed a commit to charris/numpy that referenced this pull request Jul 22, 2025
@charris charris removed the 09 - Backport-Candidate PRs tagged should be backported label Jul 22, 2025
charris added a commit that referenced this pull request Jul 22, 2025
BUG: fix casting issue in center, ljust, rjust, and zfill (#29369)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

BUG: MemoryError when using negative width in numpy.strings.xxx or numpy.char.xxx with StringDType arrays
3 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy