cookiecutter-pypackage-ttufts

An customized cookiecutter template for Python packages, and some guidelines for Python packaging.

Usage

pip install cookiecutter
git clone https://github.com/ttufts/cookiecutter-pypackage-ttufts.git
cookiecutter cookiecutter-pypackage-ttufts/

You should then change the classifiers in {{ package_name }}/setup.py - it is assumed that the project will run on the latest versions of Python 2 and 3, so you should remove any classifiers that do not apply. The full list of PyPI classifiers can be found here.

Fill out the README, and - if necessary - add a license to the project.

Explanation

The decisions cookiecutter-pypackage-ttufts makes should all be explained here.

README

• README should use reStructuredText format This is the format used by most Python tools, is expected by setuptools, and can be used by Sphinx.
• As few README files as possible Additional README files (AUTHORS, CHANGELOG, etc) should be left to the user to create when necessary.

setup.py

• Use setuptools It's the standard packaging library for Python. distribute has merged back into setuptools, and distutils is less capable.
• setup.py should not import anything from the package When installing from source, the user may not have the packages dependencies installed, and importing the package is likely to raise an ImportError.
• setup.py should be the canonical source of package dependencies There is no reason to duplicate dependency specifiers (i.e. also using a requirements.txt file). See the testing section below for testing dependencies.

Testing

• Uses pytest as the default test runner This can be changed easily, though pytest is a easier, more powerful test library and runner than the standard library's unittest.