-
Notifications
You must be signed in to change notification settings - Fork 7
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
options still not being honored #226
Comments
The options aren't honored even from the command line: shroud abispack.yaml --outdir-python abispack --option wrap_fortran=False --option wrap_python=True --option wrap_c=False (generated the same thing). |
It looks like if I add an extra $ shroud abispack.yaml --outdir-python abispack --outdir abispack And the setup.py is also generated there, at least it doesn't overwrite the one in the root anymore! But I'm wondering why the fortran, c, etc. are being generated? |
I see why the extra Fortran and C files. I made a "fix" recently that allowed |
woohoo! 🎉 Thank you @ltaylor16 ! |
tutorial.yaml was creating fortran and C wrappers because of a recent change which promoted wrap_fortran up to the top level. has_default_args was creating functions for Fortran and C when the wrapper was not requested. Add a regression test to process tutorial with only wrap_python=True. #226
I'm not sure what broke since early this morning, but I'm running the same command, and none of my options are honored - the files are generated in the root directory instead of the subfolder I specified, and all formats are produced (even though I just asked for Python). I just installed fresh from the develop branch. Here is my abispack.yaml file:
And when I run the Makefile command:
# make shroud cp setup.py _setup.py shroud abispack.yaml --outdir-python abispack .yaml
Everything is dumped in the present working directory (for all files types) AND generated in the subfolder. So maybe my options are being honored, but it's generated the default "everything" in the root anyway?
I'm guessing this was a bug introduced this morning? Sorry for the noise, this was working at around 5am and isn't anymore.
The text was updated successfully, but these errors were encountered: