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
CLI QOL Improvements #1181
Labels
Comments
cc @richafrank |
👍 |
Stack trace for the failures I'm seeing on @llllllllll's latest trying to run the quandl bundle:
|
this is a really funny issue. In python 2 when we do |
llllllllll
pushed a commit
that referenced
this issue
May 5, 2016
Fixes the issues presented in #1181 by @ssanderson around the new command line interface.
llllllllll
pushed a commit
that referenced
this issue
May 5, 2016
Fixes the issues presented in #1181 by @ssanderson around the new command line interface.
fixed with #1178 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tried to use the new CLI a bit this morning. Feedback from that experience.
python -m zipline <stuff>
, which is an annoying amount of typing. We could register an entrypoint in our setup.py so that you can just dozipline <stuff>
. In my experience, this is how most libraries bundle command line interfaces (c.f., for example,gunicorn
,ipython
orjupyter
). Click also has support for generating completion wrappers for entrypoints registered viaconsole_scripts
.__main__.py
in the usage string.python -m zipline ingest -b quandl
crashes for me infetch_symbol_metadata_frame
.zipline ingest
orzipline run
, but there's no way to see what bundles are available. Azipline bundles
entrypoint would be nice for this, which could also be used to show the dates for which you have bundles available.The text was updated successfully, but these errors were encountered: