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.18.tar.gz (545.3 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.18-py3-none-any.whl (44.5 kB view details)

Uploaded Python 3

File details

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

File metadata

  • Download URL: vscodenb-0.1.18.tar.gz
  • Upload date:
  • Size: 545.3 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.18.tar.gz
Algorithm Hash digest
SHA256 97b86f9f441ef6c590f244c8ee0068ccec3ecbff30ecb54a56612362eeb80827
MD5 7af7dbeef949783847399956589bcfb1
BLAKE2b-256 db00f3268a7ae46c7cb8f393d37f763eb3a8906620cff01b334d42dab34a0f1e

See more details on using hashes here.

File details

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

File metadata

  • Download URL: vscodenb-0.1.18-py3-none-any.whl
  • Upload date:
  • Size: 44.5 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.18-py3-none-any.whl
Algorithm Hash digest
SHA256 f91937292c2fe8276e8fb9994f99164bce97ece4f6043e47d20e8b84113b8573
MD5 f51bce01530fff3112cae8d2dc88419c
BLAKE2b-256 c82a980511a78d284734bc988f9c8b2b6aab7cb8af17f98eeb1f59a850babc10

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