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
Add @pydanny to the Cookiecutter feedstock #1
Conversation
Yeah, let's figure out the whichcraft story (which is odd, as it worked, once!), then re-kick all these... I don't think i can kick appveyor, though. |
Trigger build on whichcraft (and adding @pydanny): |
Hooray, first partial success on windows: |
Rock on @bollwyvl 🎸 Thank you! |
@willingc thanks for the gentle prodding! |
Yeah. Right on! So we have the first of the jupyter cookiecutters (we should PR that): I think we'll end up with more, as well. One thing i have been thinking about is notebook enabling cookiecutter, either as a separate project or in mainline (without the notebook dep). Basically, if we had a second json file that provided the context of the cookiecutter.json, perhaps as JSON schema (because standards 🍰) or JSON-LD context, yaml, we could create lovely, in-browser GUIs for the cookiecutter command (thinking widgets here). Will mull over this this weekend! |
Awesome! Project Jupyter has its first cookiecutter! |
More 1.5.0 updates, rerender
No description provided.