Adding infrastructure for intake projects #22
Conversation
README.md
Outdated
| Domain-specific narrative examples using multiple PyViz projects | ||
| Domain-specific narrative examples using multiple PyViz projects. | ||
| Isolated fully described projects, runnable locally and deployable | ||
| to Anaconda Enterprise. |
There was a problem hiding this comment.
Each project is expected to have an author and a date (date created or date modified? not sure), and a canonical URL that can be sent around to send someone to this particular project.
| - python=3.6 | ||
| - notebook ==5.7.8 | ||
| - ipykernel ==5.1.0 | ||
| - nomkl |
There was a problem hiding this comment.
Can you document why we suggest nomkl?
There was a problem hiding this comment.
We might want to talk about that actually. I originally did it to speed up environment set up times. But we should probably decide as a group whether or not we want nomkl in all these projects @pyviz-topics/pyviz-dev
There was a problem hiding this comment.
Usually mkl is used for better runtime performance in numpy operations, but maybe with datashader that's not so important, as we use Numba for most of the internal computations anyway?
|
Happy to insert a section about the pip+git format to get projects working off git master once the rest is ready... |
Co-Authored-By: James A. Bednar <[email protected]>
|
@jlstevens I am done pushing if you want to just add your bit to this PR? |
|
Sure! |
|
LGTM |
This work came out of #20 which is on hiatus at the moment. But this part should get in so that people can start writing and testing intake projects. Plus starts the work of documenting what I'm doing #3.