- Metadata and dependency information is stored in the pyproject.toml for compatibility with both pip and poetry.
- Flake8, pylint, and isort configurations are defined to be compatible with the black autoformatter.
- Pylint settings are based on the Google Python Style Guide and adapted for black compatibility.
- Linting tools run automatically before each commit using pre-commit, black, and isort.
- Test coverage reports are generated during every commit and pull request using coverage and pytest-cov. All reports are automatically uploaded and archived on codecov.io.
- Unit tests are written using pytest and static type checking is provided by mypy.
- Package releases to PyPI with dynamic versioning provided by bump2version begin automatically whenever a new tag is created in github.
- Documentation is built using mkdocs and mkdocstrings. Docs are automatically deployed to github pages during every release.
- Release notes are automatically generated during every release using github actions.
To install the package using pip:
pip install pytemplates_pypackageTo add the package as a dependency using poetry:
poetry add pytemplates_pypackageFrom a .py file:
import pytemplates_pypackage
print(pytemplates_pypackage.__version__)
pytemplates_pypackage.greet(user="Jacob")
from pytemplates_pypackage import wish_farewell
wish_farewell(user="Jacob")To begin local development, clone the PyTemplates/typer_cli repository and use one of the following methods to build it. Commands should be executed from inside of the project home folder.
poetry installInstall optional dependencies using the --extras flag:
poetry install --extras=environmentpip install .Install optional dependencies using square brackets:
pip install .[environment]test = [
"pytest",
"pytest-cov",
]
lint = [
"black",
"isort",
"flake8",
"pylint",
"mypy",
"pre-commit",
]
docs = [
"mkdocs",
"mkdocstrings",
"mkdocstrings-python",
"mkdocs-material",
]
# Includes all optional dependencies
dev = [
"pytest",
"pytest-cov",
"black",
"isort",
"flake8",
"pylint",
"mypy",
"pre-commit",
"mkdocs",
"mkdocstrings",
"mkdocstrings-python",
"mkdocs-material",
"bump2version",
]-
make clean- Remove all build, testing, and static documentation files. -
make test- Run the tests using pytest. -
make lint- Run the linting tools. Includes pre-commit hooks, black, isort, flake8, pylint, and mypy. -
make check- Run the test and lint commands. -
make gen-docs- Generate HTML documentation. -
make docs- Generate HTML documentation and serve it to the browser. -
make pre-release increment={major/minor/patch}- Bump the version and create a release tag. Should only be run from the main branch. Passes the increment value to bump2version to create a new version number dynamically. The new version number will be added to _version_.py and pyproject.toml and a new commit will be logged. The tag will be created from the new commit.
-
test- Run the tests on every push/pull_request to the main branch. Writes a coverage report using pytest-cov and uploads it to codecov.io. Tests run against python versions 3.8 and 3.9. Optional manual trigger in the github actions tab. -
lint- Run the linting tools on every push/pull_request to the main branch. Includes pre-commit hooks, black, isort, flake8, pylint, and mypy. Optional manual trigger in the github actions tab. -
docs- Build the documentation, publish to the docs branch, and release to github pages. Runs on a manual trigger in the github actions tab. -
release- Build a wheel distribution, build a docker image, create a github release, and publish to PyPI and Docker Hub whenever a new tag is created. Linting and testing steps must pass before the release steps can begin. Documentation is automatically published to the docs branch and hosted on github pages. All github release tags, docker image tags, and PyPI version numbers are in agreement with one another and follow semantic versioning standrads.
A release should consist of the following two steps from a tested, linted, and up to date copy of the main branch:
-
make pre-release increment={major/minor/patch}- Commit the version number bump and create a new tag locally. The version number follows semantic versioning standards (major.minor.patch) and the tag is the version number prepended with a 'v'. -
git push --follow-tags- Update the main branch with only the changes from the version bump. Publish the new tag and kick off the release workflow.
.
├── docs
│ ├── code_reference
│ │ ├── module1.md
│ │ └── module2.md
│ ├── developer_guide
│ │ ├── commands.md
│ │ ├── developer_setup.md
│ │ ├── releases.md
│ │ └── workflows.md
│ ├── extras
│ │ ├── credits.md
│ │ └── file_tree.md
│ ├── index.md
│ └── user_guide
│ ├── installation.md
│ └── usage.md
├── LICENSE
├── Makefile
├── mkdocs.yml
├── poetry.lock
├── pyproject.toml
├── README.md
├── src
│ └── pytemplates_pypackage
│ ├── core
│ │ ├── __init__.py
│ │ ├── module1.py
│ │ └── module2.py
│ ├── __init__.py
│ └── __version__.py
└── tests
├── __init__.py
├── test_module1.py
└── test_module2.py