Open mmcky opened 4 years ago
Review the current execution model and make messaging more useful.
[ ] coverage should show pass/fail stats and summary stats at the completion of the run
[ ] execution should be managed on a single dask client
for the various heterogeneous tasks provided.
[ ] consider execution environment in context of all dependencies and consider a staged execution pipeline.
[ ] consider implications for https://github.com/QuantEcon/sphinxcontrib-jupyter/issues/274
lecture1/<notebook> + files
could be easily distributed.
We are planning a review and rewrite of the extension in mid November 2019.
This will primarily target:
212
272
I have opened this issue to allow others to post their priorities for this rewrite to see if we can implement support for those features and to consider how they may fit in with a more well designed code-base.