-
-
Notifications
You must be signed in to change notification settings - Fork 11.9k
ENH: Implement f2py2e with argparse
#21923
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
base: main
Are you sure you want to change the base?
Conversation
|
I haven't read through this yet, but I approve of the goal. Having the front end use a modern standard should make f2py more maintainable. Next up, the templating :) |
b1e103e to
f388c96
Compare
HaoZeke
left a comment
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 is fantastic work, some minor comments aside. Also could you add a release note?
pearu
left a comment
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.
I did a quick review and have couple of nits.
I did not review f2pyarg.py nor service.py because it is hard to tell what is new code there and what is the result of splitting existing code into different files. Could you mark the new code in these files somehow to ease reviewing?
2836f58 to
5a44c5d
Compare
@pearu I have made the suggested changes, please have a look.
I'll add comments explaining the changes in the frontend files. |
|
I have added comments explaining step by step how the new frontend works @pearu. Please have a look and let me know any improvements or if you want further explanation. |
|
@NamamiShanker for the release notes, please create a file |
python 3.8 does not support substriptable builtin types.
This reverts commit 31ec066.
This draft PR implements the F2PY frontend with
argparselibrary. The aim is to split up one big f2py2e.py into 2 files. One filef2pyarg.pyis responsible for parsing arguments file while otherservice.pydeals withf2pycore functionalities.Some upcoming goals are:
.pyffiles.--f2py-wrapper-output,--skip-empty-wrappers