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, modulename, 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_modulename.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.8.tar.gz (434.7 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.8-py3-none-any.whl (41.7 kB view details)

Uploaded Python 3

File details

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

File metadata

  • Download URL: vscodenb-0.1.8.tar.gz
  • Upload date:
  • Size: 434.7 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.8.tar.gz
Algorithm Hash digest
SHA256 3bd521a1278424892570404375a91c05c742fc7324cd8a5d366dacb2747b4677
MD5 a6f8ef99a6558f49f4661d826aa598cf
BLAKE2b-256 a5a65e85319ebab023194ec8217a5b85933ba2accde3afecac93619c9d221a3f

See more details on using hashes here.

File details

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

File metadata

  • Download URL: vscodenb-0.1.8-py3-none-any.whl
  • Upload date:
  • Size: 41.7 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.8-py3-none-any.whl
Algorithm Hash digest
SHA256 3e14376a788edf1c619982aa057621c81f0b9bbedfb2340d7135ae4d6d8ceef9
MD5 a5b960692e94dc02cedf85d38d6cb66f
BLAKE2b-256 04c9576ae788960711b867e7fbb2518d3a7e0f7ea308907c7f436b6157d2e40d

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