Template repository for a library project
Initial set up
- In the link above, replace
librarynamewith your library's name. - Rename the
librarynamefolder to the name of your library, do not use hyphens, '-', in the name. - Replace all instances of
libraryname,vscodenb, andfunctionnamefor the names of/in your library (Shift-Cmd-Fin VScode).
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.
Metadata
Release files for vscodenb 1.0.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| vscodenb-1.0.8.tar.gz | 626.8 kB | Without provenance | Details for vscodenb-1.0.8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| vscodenb-1.0.8-py3-none-any.whl | Python 3 | none | any | Details for vscodenb-1.0.8-py3-none-any.whl |
Total release size: 674.0 kB
Release files / vscodenb-1.0.8.tar.gz
| Download URL | vscodenb-1.0.8.tar.gz |
|---|---|
| Size | 626.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
41440d3798243858c3e1171ae20197b235f4a34810afbd0da26e031f29bc086d
|
|
BLAKE2b-256 checksum How to use checksums |
18a1536fd448337c09fd87211ef879ab392512845ec4bb961ccb81ea4614a6ec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / vscodenb-1.0.8-py3-none-any.whl
| Download URL | vscodenb-1.0.8-py3-none-any.whl |
|---|---|
| Size | 47.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
11cdb93cfba4628537ae57a9d20a95e7b17dc22f580fe91fefe512cf9cde6e56
|
|
BLAKE2b-256 checksum How to use checksums |
da91b9f04ca11a01b9c3ccb1add12cab649894a8faba3a435e783097ec6297f8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for vscodenb 1.0.8
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.