-
-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
BUG: AssertError from f2py in crackfortran.py #26466
Comments
Same BUG encountered. With some simple testing I know that this would happen if After digging into the code, I think the problem is that, There is a regexp that preprocess lines and determine the type numpy/numpy/f2py/crackfortran.py Lines 586 to 589 in ea02e84
numpy/numpy/f2py/crackfortran.py Lines 643 to 644 in ea02e84
The resulting This can be fixed by explicitly match out the (optional) comment, i.e., change the corresponding regexp to: |
@HaoZeke Ping. |
Excellent, I will get to this by the weekend for sure. @RibomBalt it would be pragmatic to fix the |
Closes numpygh-26466 Since that is also related to comment parsing in F77
Closes numpygh-26466 Since that is also related to comment parsing in F77
Closes numpygh-26466 Since that is also related to comment parsing in F77
Closes numpygh-26466 Since that is also related to comment parsing in F77
Describe the issue:
When processing one of the Fortran files from the International Reference Ionosphere Software (namely
iriflip.for
) withf2py
anAssertError
is raised. I stripped most of the source code, and retained only a small snippet that still produces the same error.Reproduce the code example:
Error message:
Python and NumPy Versions:
1.26.4
3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0]
Runtime Environment:
Context for the issue:
I cannot build the python bindings to the aforementioned Fortran sources (International Reference Ionosphere Software).
A temporary work-around is that I preprocess the Fortran source files by stripping all comments, e.g.:
The text was updated successfully, but these errors were encountered: