Closed jsignell closed 5 years ago
Ok, sounds good.
The docs for pyviz-topics/examples should also show how one should develop such projects, when going back and forth between editing projects and editing the modules on which the projects are based. @jlstevens can write this, showing how to use pip specifications for the master branch of a module in anaconda-project, for development before the conda package is ready for release.
Assigning myself this issue too as a reminder to do the pip+git documentation mentioned above.
I have now added a section detailing how to use pip+git in PR #22.
Closed by #22
Right now I have a developer env with nbrr, tornado<0.5, and anaconda-project (this should be captured in an env spec.
I have been doing something like:
Then I go into anaconda-project.yml, delete all the comments and reorganize it to look like the nice versions.
So I guess I should create a template that can be used by
nbrr
,anaconda-project
, orpyctdev
/doit
.