-
-
Notifications
You must be signed in to change notification settings - Fork 10.9k
BUG: Infer return types for Fortran functions in f2py
#23600
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
Conversation
This looks good, but I don't really know fortran. @melissawm could you have a brief look? Should this be backported? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me, @HaoZeke - thanks! I also checked against SciPy and it looks good.
@@ -4,6 +4,6 @@ SUBROUTINE FOO(N) | |||
Cf2py integer optional,intent(in) :: n = 13 | |||
REAL A,X | |||
COMMON /DATA/ A,X(3) | |||
PRINT*, "IN FOO: N=",N," A=",A," X=[",X(1),X(2),X(3),"]" | |||
C PRINT*, "IN FOO: N=",N," A=",A," X=[",X(1),X(2),X(3),"]" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we want to remove this line entirely?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ack, sorry, didn't see this earlier, I'll open a general cleanup to make sure we have no print statements in the f2py
tests this weekend.
Thanks, will just put it in tomorrow (or someone else please do)! I don't see an obvious reason for backport anywhere, but if there is, please label it. |
Thanks again @HaoZeke. |
Closes #23598.