cinterop 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 cinterop
Release steps¶
- all UT pass
- Merge new features/fixes to devel branch.
- version.py updated
- check readme is up to date
Code¶
If need a separate conda env
conda create --name ${my_env_name} python=3.6
conda activate ${my_env_name}
conda install wheel twine six pytest
conda activate ${my_env_name}
cd ${HOME}/src/c-interop/bindings/python/cinterop
rm dist/*
python setup.py sdist bdist_wheel
rm dist/*.tar
Importantly to not end up with incorrect display of the readme:
Then and only then:
Documentation¶
2021-01 Exploring options for putting this on readthedoc. 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).
Starting afresh with this, reading the RTD guides. Introduces mkdocs. Notice this blog on mkdocs-material which seems like the new cool kid on the block.
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
mamba install -c conda-forge 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)