Skip to main content

Best practicses for Python projects

Project description


CircleCI travis codecov Code style: black awesome PyPI pyversions PyPi Version GitHub stars PyPi downloads

A Python project template that highlights some best practices in Python packaging. Can be used as a GitHub template for your new Python project.

Best practices

  • The name of the git repo should be the PyPi name of the package should be what you you type as import mypackagename. That means no hyphens in package names!

  • Your package should be a one-trick pony. Nobody wants to install a huge toolbox if all they need is the image converter in it.

  • After import yourpackagename, people should be able to call yourpackagename.__version__ plus some other meta data. This helps with debugging.

  • Choose a license for your code and provide a LICENSE[.txt] in the root level of your package as well as a statement in your main README. can help you make a decision.

  • Use linting and formatting, include those in your integration tests.

    • black is a formatter that I like because you cannot configure it -- black is black.
    • Good linters are flake8 and pylint.
    • isort sorts your imports alphabetically.
  • Once you have tests in order, make sure they are executed with every git push. Two popular CI services that run your tests are travis and circleci. This repository contains the config files for each of the two.

  • Make sure that nobody can push to master. On GitHub, go to Settings -> Branches -> Add rule and select Require status checks to pass before merging and Include administrators. Development happens in pull requests, this makes sure that nobody -- including yourself -- ever accidentally pushes something broken to master.

  • Use a tool for measuring test coverage. codecov is one, and the circleci config submits the data to it.

  • If you have CI set up, want to show test coverage, or advertise the availability on PyPi, do so using a badge at the top of your README. Check out for what's available.

  • Include contributing guidelines and a code of conduct (edit to add appropriate enforcement contacts or use a template) to help foster a community.

What you can do with this template

First run

find . -type f -print0 -name "*.py" -o -name Makefile -o -name "*.yml" | xargs -0 sed -i 's/pyfoobar/your-project-name/g'

and rename the folder pyfoobar to customize the name.

There is a simple Makefile that can help you with certain tasks:

  • Run make format to apply formatting.

  • Run make check to check formatting and style.

  • Run make publish to

    • tag your project on git (make tag)
    • upload your package to PyPi (make upload)

    After publishing, people can install your package with

    pip3 install --user pyfoobar


To run the pyfoobar unit tests, check out this repository and type



pyfoobar is published under the MIT license.

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Files for pyfoobar, version 0.0.4
Filename, size File type Python version Upload date Hashes
Filename, size pyfoobar-0.0.4-py3-none-any.whl (5.7 kB) File type Wheel Python version py3 Upload date Hashes View
Filename, size pyfoobar-0.0.4.tar.gz (5.4 kB) File type Source Python version None Upload date Hashes View

Supported by

Pingdom Pingdom Monitoring Google Google Object Storage and Download Analytics Sentry Sentry Error logging AWS AWS Cloud computing DataDog DataDog Monitoring Fastly Fastly CDN DigiCert DigiCert EV certificate StatusPage StatusPage Status page