A Python package cookiecutter with modern tooling.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Luke Murphy 4f828833b2
Use more standard docs folder
3 weeks ago
{{cookiecutter.package}} Use more standard docs folder 3 weeks ago
LICENSE Use the correct license 8 months ago
README.rst Integrate liberapay 3 weeks ago
cookiecutter.json Integrate liberapay 3 weeks ago

README.rst

pypkgtemplate

Support badge

A Python package cookiecutter with modern tooling

Why another template?

A lot of cookiecutter template designers try to include all the things from the start and then due to maintenance burdens, the package fall behind with the moving ecosystem. For example, one of the most commonly used packages, cookiecutter-pypackage has, at present moment, not been updated for a year and has 23 open change requests.

This template is about moving with the ecosystem to provide a modern and up-to-date cookiecutter template for creating Python packages. In order to keep up to speed, I focus on tooling configuration rather than code customisation. Your Python package code can be different each time but the tools should be standardised and reliable.

Design Principles

  • Make no assumptions about the Python package code (different every time)
  • Use standardised tooling for packaging and dependencies (setuptools, twine).
  • Use best-in-class tooling for testing (tox, pytest, coverage)
  • Use best-in-class tooling for documentation (sphinx, towncrier, reStructuredText, readthedocs)
  • Use best-in-class tools for quality assurance (flake8, isort, mypy, black)
  • Use best-in-class community financial funding platforms (Liberapay)
  • Use community and maintenance aids (CoC templates, issue templates)
  • Provide common CI configurations (Travis CI)
  • Use GPL version 3+ for the license.

Usage

Install cookiecutter and then invoke the following spell:

cookiecutter https://hack.decentral1.se/decentral1se/pypkgtemplate.git

Then you manually need to create your readthedocs project.

Refer to CONTRIBUTING.rst for the developer interface.

Variables

{
    "package": "",
    "organisation": "",
    "author": "",
    "author_email": "",
    "author_site": "",
    "git_hosting_url": "",
    "package_description": "",
    "liberpay_username": ""
}
  • package: The package name.
  • organisation: The organisation name (for CoC, URLs, etc).
  • author: The package creator.
  • author_email: The package creator's email.
  • author_site: The package creator's website.
  • git_hosting_url: The git hosting URL of the package.
  • package_description: The package short description.
  • liberapay_username: The package creator's Liberpay username.