-
Notifications
You must be signed in to change notification settings - Fork 9
Home
Weixiang Yu edited this page Dec 8, 2023
·
8 revisions
- Create a new mamba env with a specific python version (e.g., 3.8) and activate
- Install Poetry
- Config poetry to create virtual env in project folder with:
poetry config virtualenvs.in-project true
- Remove existing
poetry.lock
file - Re-install everything with
poetry install
; note that this command will automatically creating a new virtual env matching the python version in the toml file.
Warning: If you are using pythons installed with conda and your base python version is different from the designated python version used above, you need to deactivate the conda virtual environment before running
poetry install
. This is to make sure that poetry will install everything in a new and isolated virtual env.
- Checkout a new branch
- Start with the '00_template' notebook in the dev folder; must add the current commit hash
- Develop within the notebook (if possible)
- Update the code base with the new feature
- Add/Update tests (if needed)
- Add/Update documentation (if needed)
- Run tests locally to make sure everything works
poetry run nox
- Push branch to remote and create a new pull request
- Merge
Note: If you use conda to manage multiple versions of python, the path to the python executable may not be included in the
$PATH
env variable, sonox
will complain about not able find the interpreter for the specific python versions. One solution is creating soft links in~/.local/bin
pointing to the corresponding conda python executables.
- Checkout a new branch (name it with the new version number, no dot)
- Update the 'pyproject.toml' to the new version number
- Update changelog
- Update 'docs/requirement.txt' and 'environment.yml' (for mybinder)
- Push branch to remote and create a new pull request
- Merge
- Update mybinder link in readme
- Add/push version tag
git tag v1.2.3
&git push origin v1.2.3
- Create a new release
- Click the mybinder link to build image