Skip to content

BUG: f2py: thread-safe forcomb (#29091) #29099

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
May 31, 2025

Conversation

charris
Copy link
Member

@charris charris commented May 31, 2025

Backport of #29091.

Closes #29086

There are zero tests for this (you could add a syntax error and the numpy test suite would still pass).
With my complete lack of knowledge of fortran, I'm unable to write one.

Tested in scipy: scipy/scipy#23084

@charris charris added this to the 2.3.0 release milestone May 31, 2025
@charris charris added 00 - Bug component: numpy.f2py 08 - Backport Used to tag backport PRs 39 - free-threading PRs and issues related to support for free-threading CPython (a.k.a. no-GIL, PEP 703) labels May 31, 2025
@charris charris merged commit 9a26c63 into numpy:maintenance/2.3.x May 31, 2025
73 checks passed
@charris charris deleted the backport-29091 branch May 31, 2025 16:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
00 - Bug 08 - Backport Used to tag backport PRs 39 - free-threading PRs and issues related to support for free-threading CPython (a.k.a. no-GIL, PEP 703) component: numpy.f2py
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants