Home

Awesome

Python Packages Project Generator

<div align="center">

Build status Dependencies Status πŸš€ Your next Python package needs a bleeding-edge project structure.

Code style: black Pre-commit Semantic Versions License Coverage Report

Your next Python package needs a bleeding-edge project structure.

</div>

TL;DR

cookiecutter gh:TezRomacH/python-package-template --checkout v1.1.1

All you need is the latest version of cookiecutter πŸ˜‰

πŸš€ Features

In this cookiecutter πŸͺ template we combine state-of-the-art libraries and best development practices for Python.

Development features

Deployment features

Open source community features

🀯 How to use it

Installation

To begin using the template consider updating cookiecutter

pip install -U cookiecutter

then go to a directory where you want to create your project and run:

cookiecutter gh:TezRomacH/python-package-template --checkout v1.1.1

Input variables

Template generator will ask you to fill some variables.

The input variables, with their default values:

ParameterDefault valueDescription
project_namepython-projectCheck the availability of possible name before creating the project.
project_descriptionbased on the project_nameBrief description of your project.
organizationbased on the project_nameName of the organization. We need to generate LICENCE and to specify ownership in pyproject.toml.
licenseMITOne of MIT, BSD-3, GNU GPL v3.0 and Apache Software License 2.0.
minimal_python_version3.7Minimal Python version. One of 3.7, 3.8 and 3.9. It is used for builds, GitHub workflow and formatters (black, isort and pyupgrade).
github_namebased on the organizationGitHub username for hosting. Also used to set up README.md, pyproject.toml and template files for GitHub.
emailbased on the organizationEmail for CODE_OF_CONDUCT.md, SECURITY.md files and to specify the ownership of the project in pyproject.toml.
version0.1.0Initial version of the package. Make sure it follows the Semantic Versions specification.
line_length88The max length per line (used for codestyle with black and isort). NOTE: This value must be between 50 and 300.
create_example_templatecliIf cli is chosen generator will create simple CLI application with Typer and Rich libraries. One of cli, none

All input values will be saved in the cookiecutter-config-file.yml file so that you won't lose them. πŸ˜‰

Demo

Demo of github.com/TezRomacH/python-package-template

More details

Your project will contain README.md file with instructions for development, deployment, etc. You can read the project README.md template before.

Initial set up

Initialize poetry

By running make install

After you create a project, it will appear in your directory, and will display a message about how to initialize the project.

Initialize pre-commit

By running make pre-commit-install. Make sure to set up git first via git init.

Package example

Want to know more about Poetry? Check its documentation.

<details> <summary>Details about Poetry</summary> <p>

Poetry's commands are very intuitive and easy to learn, like:

etc

</p> </details>

CLI example

If you set create_example_template to be cli the template comes with a cute little CLI application example. It utilises Typer and Rich for CLI input validation and beautiful formatting in the terminal.

After installation via make install (preferred) or poetry install you can try to play with the example:

poetry run <project_name> --help
poetry run <project_name> --name Roman

Building and releasing your package

Building a new version of the application contains steps:

Makefile usage

Makefile contains a lot of functions for faster development.

<details> <summary>1. Download and remove Poetry</summary> <p>

To download and install Poetry run:

make poetry-download

To uninstall

make poetry-remove
</p> </details> <details> <summary>2. Install all dependencies and pre-commit hooks</summary> <p>

Install requirements:

make install

Pre-commit hooks coulb be installed after git init via

make pre-commit-install
</p> </details> <details> <summary>3. Codestyle</summary> <p>

Automatic formatting uses pyupgrade, isort and black.

make codestyle

# or use synonym
make formatting

Codestyle checks only, without rewriting files:

make check-codestyle

Note: check-codestyle uses isort, black and darglint library

Update all dev libraries to the latest version using one comand

make update-dev-deps
</p> </details> <details> <summary>4. Code security</summary> <p>
make check-safety

This command launches Poetry integrity checks as well as identifies security issues with Safety and Bandit.

make check-safety
</p> </details> <details> <summary>5. Type checks</summary> <p>

Run mypy static type checker

make mypy
</p> </details> <details> <summary>6. Tests with coverage badges</summary> <p>

Run pytest

make test
</p> </details> <details> <summary>7. All linters</summary> <p>

Of course there is a command to rule run all linters in one:

make lint

the same as:

make test && make check-codestyle && make mypy && make check-safety
</p> </details> <details> <summary>8. Docker</summary> <p>
make docker-build

which is equivalent to:

make docker-build VERSION=latest

Remove docker image with

make docker-remove

More information about docker.

</p> </details> <details> <summary>9. Cleanup</summary> <p> Delete pycache files
make pycache-remove

Remove package build

make build-remove

Delete .DS_STORE files

make dsstore-remove

Remove .mypycache

make mypycache-remove

Or to remove all above run:

make cleanup
</p> </details>

🎯 What's next

Well, that's up to you πŸ’ͺ🏻. I can only recommend the packages and articles that helped me.

Articles:

πŸ“ˆ Releases

You can see the list of available releases on the GitHub Releases page.

We follow Semantic Versions specification.

We use Release Drafter. As pull requests are merged, a draft release is kept up-to-date listing the changes, ready to publish when you’re ready. With the categories option, you can categorize pull requests in release notes using labels.

List of labels and corresponding titles

LabelTitle in Releases
enhancement, featureπŸš€ Features
bug, refactoring, bugfix, fixπŸ”§ Fixes & Refactoring
build, ci, testingπŸ“¦ Build System & CI/CD
breakingπŸ’₯ Breaking Changes
documentationπŸ“ Documentation
dependencies⬆️ Dependencies updates

πŸ§ͺ TODOs

This template will continue to develop and follow the bleeding edge new tools and best practices to improve the Python development experience.

Here is a list of things that have yet to be implemented:

πŸ›‘ License

License

This project is licensed under the terms of the MIT license. See LICENSE for more details.

πŸ… Acknowledgements

This template was inspired by several great articles:

and repositories:

Give them your ⭐️, these resources are amazing! πŸ˜‰

πŸ“ƒ Citation

@misc{python-package-template,
  author = {Roman Tezikov},
  title = {Python Packages Project Generator},
  year = {2020},
  publisher = {GitHub},
  journal = {GitHub repository},
  howpublished = {\url{https://github.com/TezRomacH/python-package-template}}
}

Markdown source for the badge πŸš€ Your next Python package needs a bleeding-edge project structure.

[![πŸš€ Your next Python package needs a bleeding-edge project structure.](https://img.shields.io/badge/python--package--template-%F0%9F%9A%80-brightgreen)](https://github.com/TezRomacH/python-package-template)