Skip to content


Switch branches/tags

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time


Forked from cookiecutter template for a Python package. Forked from audreyr/cookiecutter-pypackage + tony/cookiecutter-pypackage-pythonic.

It is inspired by flask and werkzeug's project style patterns. It is used on the tmuxp, cihai-python and vcspull projects. The app object is based on early versions pypa/warehouse, when it used werkzeug (see warehouse's old app object).

  • Free software: BSD license
  • Vanilla testing setup with unittest and python test
  • Travis-CI: Ready for Travis Continuous Integration testing
  • Tox testing: Setup to easily test for Python 2.6, 2.7, 3.3
  • Sphinx docs: Documentation ready for generation with, for example, ReadTheDocs. Note: You can install sphinx docs requirements with $ pip install -r docs/requirements.txt.

Additions and changes

  • (feature) app factory can be configured with ini, yaml or json (pypa/warehouse, cihai style) and by specifying options via CLI. Flask-Script only supports -c config_file. Application factory can be wired to support option args and config file (pypa/warehouse, cihai)
  • (feature / removal) - use flask testing client for tests, remove dependency on flask-testing.
  • (feature) config file declaratively pulls blueprints from python paths add them in the app factory.
  • (coverage) unittests against flask api, blueprint example module.


  • flask/werkzeug-style testsuites. See werkzeug testsuite on github.

  • Use to run all tests, or pass in arguments to test a particular TestSuite, TestCase or Test:

    $ ./
    $ ./ yourpackage
    $ ./ repo_name.repo_name  # package_name.TestSuite
    $ ./ yourpackage.testsuite.test_something
    $ ./ testsuite.test_something
    $ ./ test_something
    $ ./ test_something test_something_docstring
  • downloads unittest2 for python 2.6.

Python 2.7+3.3

  • from __future__ import absolute_import, division, print_function, \
        with_statement, unicode_literals
  • repo_name/ module (derived from flask, werkzeug and jinja2.) Why a compatibility module? See Armin Ronacher's post Porting to Python 3 Redux.


  • repo_name/ + repo_name/ Metadata in repo_name/ e.g. __title__, __author__ can be accessed via:

    >>> about = {}
    >>> with open("repo_name/") as fp:
    >>>     exec(, about)
    >>> print(about['__title__'])
    Your project name

    Keeps and doc/ in sync with package metadata. pypi and readthedocs distributions build off the latest package data.

    This method avoids cost of tokenizing and importing python file and avoids encountering potential import errors that may arise. It simply opens a vanilla python file and evals it.

    Derived from pypa/warehouse.

  • Relative imports in repo_name/

  • Relative imports in repo_name/testsuite/

  • Relative imports in repo_name/testsuite/{{ cookiecutter.package_name }}.py.


  • README.rst reStructuredText table for project information.
  • vim modelines for rst in TODO and CHANGELOG.
  • docs/requirements.txt, which can be targetted to install sphinx changelog package on ReadTheDocs. It will also trigger -r ../requirements.txt.
  • sphinx changelog module, (imitation of sqlalchemy, see sqlalchemy changelog)
  • Add TODO and docs/roadmap.rst.
  • Rename CHANGELOG.rst -> CHANGELOG.
  • Add docs/api.rst for documentation of API code. Initial class imported with docstring example.
  • Automatically generate header spacing based on length of cookiecutter variables.

Example data

  • Example TestCase.
  • Example Class w/ docstrings.


Install cookiecutter:

$ sudo pip install cookiecutter

Generate a Python package project:

$ cookiecutter


Not Exactly What You Want?

Don't worry, you have options:

Similar Cookiecutter Templates


$ pip install -r dev-requirements.txt
$ sniffer
# edit any file in {{cookiecutter.repo_name}}
# todo: add for one-time runs

Fork This / Create Your Own

If you have differences in your preferred setup, I encourage you to fork this to create your own version. Or create your own; it doesn't strictly have to be a fork.

  • Once you have your own version working, add it to the Similar Cookiecutter Templates list above with a brief description.
  • It's up to you whether or not to rename your fork/own version. Do whatever you think sounds good.

Or Submit a Pull Request

I also accept pull requests on this, if they're small, atomic, and if they make my own packaging experience better.


Pythonic starter boilerplate for Flask







No releases published


No packages published