Skip to main content

Utilities and styling for notebooks in vscode

Project description

Template repository for a library project

Initial set up

  • In the link above, replace libraryname with your library's name.
  • Rename the libraryname folder to the name of your library, do not use hyphens, '-', in the name.
  • Replace all instances of libraryname, vscodenb, and functionname for the names of/in your library (Shift-Cmd-F in VScode).

example event parameter

Development

In addition to any dependencies of your library, the development setup requires quarto the following packages:

conda-forge::jupyter conda-forge::nbconvert conda-forge::quartodoc conda-forge::gh conda-forge::git conda-forge::pip

Version

The only version you need to change is the one in setup.cfg.

Unit tests

Test are put in test/test_vscodenb.py. Run these and all other test_* files you create by running ./scripts/test.sh.

Creating docs

Use type hits (with the typing module) for code and add this to your settings.json in VScode.

"files.associations": {
    "*.qmd": "quarto"
},
"autoDocstring.docstringFormat": "numpy",
"autoDocstring.startOnNewLine": true,
"autoDocstring.customTemplatePath": "docs/autodoc.mustache",

That lets you can autogenerate doc-strings by typing """ at the top of your functions.

Publishing docs

Docs are published to your github pages site https://{user}.github.io/{libraryname}. The template is set up for the user munch-group, but you can substitute all its instances for your own github user name.

Run all documentation notebooks inplace by running ./docs-run-notebooks.sh. Build and render all documentation by running ./docs-build-render.sh.

Publishing conda package

Once pushed to github the library can be published as a conda package by running ./conda-release.sh.

Publishing the conda package to anaconda requires that you set up a github secret, ANACONDA_TOKEN, that you create on your anaconda.org account.

Library dependencies

Dependencies are managed in pyproject.toml and automatically read by conda-build/meta.yaml.

Entry points

Entry points are defined in pyproject.toml and automatically read by conda-build/meta.yaml.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

vscodenb-0.1.33.tar.gz (627.0 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

vscodenb-0.1.33-py3-none-any.whl (44.9 kB view details)

Uploaded Python 3

File details

Details for the file vscodenb-0.1.33.tar.gz.

File metadata

  • Download URL: vscodenb-0.1.33.tar.gz
  • Upload date:
  • Size: 627.0 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.13.7

File hashes

Hashes for vscodenb-0.1.33.tar.gz
Algorithm Hash digest
SHA256 7220fad4a9a058b27e448c1bc2278f3c6da70ea7ec9ca099e92602889757aedf
MD5 bf3f2058caf78089c42b01f5aad74ebe
BLAKE2b-256 e7a5d2f165b68cfd1238ff1392de2e4a27095ca2fac38af6e0230ea589271854

See more details on using hashes here.

File details

Details for the file vscodenb-0.1.33-py3-none-any.whl.

File metadata

  • Download URL: vscodenb-0.1.33-py3-none-any.whl
  • Upload date:
  • Size: 44.9 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.13.7

File hashes

Hashes for vscodenb-0.1.33-py3-none-any.whl
Algorithm Hash digest
SHA256 6600d4397741548e7d0726256e4fe001ac857f2bbd5371f5084b15f6283ac64a
MD5 6b7557910a6fa620e9f9f01a882e8b21
BLAKE2b-256 f9f230fa32bd5b5427492bb2947a5392d79cdce48501955eb749a93ea781e4a9

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page