package tech notes¶
These are notes for the package maintainer(s). Most users can ignore them.
Note to self: as of Jan 2019 also using github_jm\didactique\doc\know_how.md to log the exploratory and release processes around refcount
Release steps¶
- all UT pass
- Merge new features/fixes to devel branch.
- version.py updated
- check readme is up to date
Code¶
# conda create --name ${my_env_name} python=3.6
conda activate ${my_env_name}
conda install wheel twine six pytest
Importantly to not end up with incorrect display of the readme:
Test locally with pip install --force-reinstall dist/lakeoned-0.1-py2.py3-none-any.whl
Then and only then:
Documentation¶
2023-01: I used in the past sphinx with napoleon extensions to document ela. This was a trial run. Did something more substantial for an internal project (WAA). Since then came accross mkdocs, which at some point was better at handling markdown than sphinx based documentation (may not be as true now). Noticed this blog on mkdocs-material.
Unclear from RTD where to create a new mkdocs project (supposed to be in the root of the python package?) not sure. for now:
mamba install -c conda-forge mkdocs-material mkdocstrings mkdocs-material-extensions
Troubleshooting¶
Can view with the retext
program (did not find VScode RST extensions working, or giving out blank output if not, perhaps)