-
-
Notifications
You must be signed in to change notification settings - Fork 10.8k
BUG: f2py wraps private
entities
#23879
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
Labels
Comments
private
entities private
entities
private
entities private
entities
HaoZeke
added a commit
to HaoZeke/numpy
that referenced
this issue
Jun 17, 2023
By adding them to skipfuncs
HaoZeke
added a commit
to HaoZeke/numpy
that referenced
this issue
Jun 17, 2023
charris
pushed a commit
to charris/numpy
that referenced
this issue
Jul 6, 2023
By adding them to skipfuncs
charris
pushed a commit
to charris/numpy
that referenced
this issue
Jul 6, 2023
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the issue:
Fortran modules can have
private
andpublic
procedures. The first can only be accessed inside the module, the latter can be used outside.f2py does not recognize
private
procedures as such and builds wrappers for them anyway, leading to a subsequent compilation error.The example below shows a module with one public (
foo
) and one private (bar
) subroutine. The pyf file shows that f2py wrappedbar
even though this subroutine is private and cannot be accessed outside.Reproduce the code example:
Error message:
Runtime information:
Context for the issue:
No response
The text was updated successfully, but these errors were encountered: