Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upSeparate Notebooks? #46
Comments
This comment has been minimized.
This comment has been minimized.
|
@edsu for modules, are you thinking something like a separate repo, that's a library, and we can release on PyPi, then pull it in? |
This comment has been minimized.
This comment has been minimized.
|
I think that's what we should aim for. Maybe add that as a separate issue. Since I think it would be easier to make the library work with the current notebook and then separate after. |
This comment has been minimized.
This comment has been minimized.
|
Another idea is to invite people to submit their own notebooks? |
This comment has been minimized.
This comment has been minimized.
|
Maybe the module could start here and then migrate if needed? I do like the idea of splitting up this large notebook into smaller ones so it can load in GitHub and generally be more manageable. Like you said I think it could set a good precedent for other people to add new ones via a pull request. |
greebie
self-assigned this
Apr 11, 2019
This comment has been minimized.
This comment has been minimized.
|
Okay now that the module is added, I'll work on this issue. I'll go with
The domains notebook is likely to be very short. I wonder if there is anything else we can include there? Maybe dates? |
edsu commentedMar 23, 2019
Thanks for putting these excellent examples together @greebie! I wonder if it might make sense moving forward to create separate notebooks for each use case, and if there are functions or bits of code that need to be shared perhaps they could be moved into a module that they all can use?