-
Notifications
You must be signed in to change notification settings - Fork 488
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
How to guide for developing nbdev #1021
Comments
I updated the title to make this a more general docs issue. BTW our recommended way to develop is to git clone nbdev and then |
Oh also we'd generally recommend also installing fastcore and execnb in this way too, since they're the key deps of nbdev and changes to them needed for nbdev are committed together. The core team all use a little script that does a |
In the nbdev development guide we might also want to touch on quarto development. @jjallaire kindly shared these recommended resources:
...and he also shared some dev/debugging tips:
|
@jph00 Is this using a copy of conda/conda-build#4251 (comment) seems to suggest that one might want (using
but as I'm new to nbdev, I'm not particularly confident of that... |
I wrote:
FWIW, this does seem to work. |
Sorry @dmose I don't understand your question. The core devs do indeed use conda, except we use |
aka "runs with scissors"
Document how to develop and test with pre-release versions of nbdev and the primary dependencies (i.e. quarto, jupyter), all of which are actively being developed.
Some topics to potentially include:
Describe how to preview locally using a prerelease version of nbdev (head or a particular commit)
For example:
Describe how to deploy to GitHub using a prerelease version of nbdev and/or quarto
workflows/deploy.yaml
The text was updated successfully, but these errors were encountered: