-
Notifications
You must be signed in to change notification settings - Fork 8
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
Confusion over name - PHEnix or Phoenix ? #2
Comments
We do not have a runnable If used in python to import modules we felt its also more appropriate and readable to have statement like Thanks for the notice on the docs not correctly reflecting the name in the repo. @ALL can we correct the docs. |
I would rename your two main scripts to You want to avoid name clashes, and it provides a single place to get a As per https://gigascience.biomedcentral.com/articles/10.1186/2047-217X-2-15 ;-) |
I think that could work nicely. We'll look into it and maybe use the nesting parsers feature of argparse (https://pymotw.com/2/argparse/#nesting-parsers). |
Just added phenix.py with the command subparsers. Have not implemented |
It would be good to transfer the updated instructions reflected in readthedocs to the README.md |
No need, it's automatically done via the docs build system: http://phenix.readthedocs.org/en/latest/scripts/modules.html |
The README.md on the front page still reflects the old way of calling the scripts |
Oh yeah, totally forgot about that. :) |
|
The repo is called
PHEnix
but the docs call itPhoenix
.And the repo doesn't have a runnable command called either of those? eg.
phenix
The text was updated successfully, but these errors were encountered: