-
Notifications
You must be signed in to change notification settings - Fork 16
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
Platform specfic parse issues #5
Comments
I suspect that at least one version of docopt that you are using is a pre-release version. Please submit |
Anyway, you need an empty line between usage-section and options-section. I suspect that that can fix it. |
For some reason the empty line did not fix it . The OSX and Linux "versions" had different checksums . I ended up uninstalling the failing Linux version and installing the OSX version in Linux. Its all working after that. Incidentally the test case also fails on the web version at try.docopt.org. I was wondering if it is possible to have a debug option so I know where the parse is failing. |
Note that For the next release–debugability is the priority. |
Hi ,
I have a docopt string like
"""Get PAM list
Usage:
list_vals_for_prot_sp.py <length_guide> <sense|antisense|all> [--chrom=CHROM_NUM default is all]
Options:
-h --help Show this screen.
"""
This parses a command like the one given below on MacOSX running 2.7.6 and docopt 0.6.1 just fine. It fails completely and just shows me the help text on Ubuntu also running Python 2.7.6 and docopt 0.6.1. Everything is identical and I am wondering why the parser behavior changes between Linux and MacOSX.
python list_vals_for_prot_sp.py 22 all
Parses file : python 2.7.6 OSX
Fails to parse : python 2.7.6 OSX
Thanks
The text was updated successfully, but these errors were encountered: