Skip to content
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

Improve notebook dependencies fetch utility #234

Closed
mmcky opened this issue Mar 14, 2016 · 2 comments
Closed

Improve notebook dependencies fetch utility #234

mmcky opened this issue Mar 14, 2016 · 2 comments

Comments

@mmcky
Copy link
Contributor

mmcky commented Mar 14, 2016

  1. Incorporate a cache mechanism so that files don't always need to be fetched (using contents of files)
@mmcky
Copy link
Contributor Author

mmcky commented Mar 15, 2016

Currently the implemented nb_fetch_dependencies() function is a simple utility that defaults to fetching files from dependencies folder in QuantEcon.notebooks repo. It does also allow fetching files from other locations such as QuantEcon.applications but becomes more difficult to specify with repo= and folder arguments etc. when the files live in other locations. This works for now and @oyamad has used this utility in a recent notebook - but could be improved upon.

We will stick with this for the time being - but we could improve this utility:

  1. swap to using https://github.com/ellisonbg/antipackage (with Cache features etc) [Con: files then get stored in a user cache and isn't directly accessible to the end user, Pro: has cache support etc]
  2. improve the current nb_fetch_dependencies() method
  3. explore constructing a Jupyter magic command that could import the dependency file(s) from a web location.

@mmcky
Copy link
Contributor Author

mmcky commented Aug 3, 2017

The current utility has been generalized and this issue can be closed.

@mmcky mmcky closed this as completed Aug 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant