PyScaffold helps you to easily setup a new Python project, it is as easy as:
putup my_project
This will create a new folder my_project
containing a perfect project template with everything you need for some serious coding.
Type putup -h
to learn about more configuration options. PyScaffold assumes that you have Git installed and set up on your PC, meaning at least your name and email configured. The project template in my_project
provides you with following features:
All configuration can be done in setup.cfg
like changing the description, url, classifiers and even console scripts of your project. That means in most cases it is not necessary to tamper with setup.py
.
In order to build a source, binary or wheel distribution, just run python setup.py sdist
, python setup.py bdist
or python setup.py bdist_wheel
.
Package and Files Data
Additional data, e.g. images and text files, inside your package can be configured under the [files]
section in setup.cfg
. It is not necessary to have a MANIFEST.in
file for this to work.
Your project is already an initialised Git repository and setup.py
uses the information of tags to infer the version of your project with the help of setuptools_scm. To use this feature you need to tag with the format MAJOR.MINOR[.PATCH]
, e.g. 0.0.1
or 0.1
. Run python setup.py --version
to retrieve the current PEP440-compliant version. This version will be used when building a package and is also accessible through my_project.__version__
.
Unleash the power of Git by using its pre-commit hooks. This feature is available through the --with-pre-commit
flag. After your project's scaffold was generated, make sure pre-commit is installed, e.g. pip install pre-commit
, then just run pre-commit install
.
It goes unsaid that also a default .gitignore
file is provided that is well adjusted for Python projects and the most common tools.
Build the documentation with python setup.py docs
and run doctests with python setup.py doctest
. Start editing the file docs/index.rst
to extend the documentation. The documentation also works with Read the Docs.
The Numpy and Google style docstrings are activated by default. Just make sure Sphinx 1.3 or above is installed.
Run python setup.py test
to run all unittests defined in the subfolder tests
with the help of py.test and pytest-runner. Some sane default flags for py.test are already defined in the [pytest]
section of setup.cfg
. The py.test plugin pytest-cov is used to automatically generate a coverage report. It is also possible to provide additional parameters and flags on the commandline, e.g., type:
python setup.py test --addopts -h
to show the help of py.test.
JUnit and Coverage HTML/XML
For usage with a continuous integration software JUnit and Coverage XML output can be activated in setup.cfg
. Use the flag --with-travis
to generate templates of the Travis configuration files .travis.yml
and tests/travis_install.sh
which even features the coverage and stats system Coveralls. In order to use the virtualenv management and test tool Tox the flag --with-tox
can be specified.
Add the requirements of your project to requirements.txt
and test-requirements.txt
which will be automatically used by setup.py
. This also allows you to easily customize a plain virtual environment with:
pip install -r requirements.txt -r test-requirements.txt
All licenses from choosealicense.com can be easily selected with the help of the --license
flag.
Create a Django project with the flag --with-django
which is equivalent to django-admin.py startproject my_project
enhanced by PyScaffold's features.
With the help of Cookiecutter it is possible to customize your project setup. Just use the flag --with-cookiecutter TEMPLATE
to use a cookiecutter template which will be refined by PyScaffold afterwards.
Creates a Vagrant folder within the project with a vagrant build as specified by the flag --with-vagrant
which is equivalent to running cd vagrant && vagrant init my_vagrant_box
.
Keep your project's scaffold up-to-date by applying putput --update my_project
when a new version of PyScaffold was released. An update will only overwrite files that are not often altered by users like setup.py. To update all files use --update --force
. An existing project that was not setup with PyScaffold can be converted with putup --force existing_project
. The force option is completely safe to use since the git repository of the existing project is not touched!