Projects set up with PyScaffold feature an easy package configuration with
setup.cfg. Check out the example below as well as PBR’s usage manual.
[metadata] name = my_project summary = A test project that was set up with PyScaffold author = Florian Wilhelm author-email = [email protected] license = new BSD home-page = http://... description-file = README.rst # Add here all kinds of additional classifiers as defined under # https://pypi.python.org/pypi?%3Aaction=list_classifiers classifiers = Development Status :: 5 - Production/Stable, Topic :: Utilities, Programming Language :: Python, Programming Language :: Python :: 2, Programming Language :: Python :: 2.7, Programming Language :: Python :: 3, Programming Language :: Python :: 3.3, Programming Language :: Python :: 3.4, Environment :: Console, Intended Audience :: Developers, License :: OSI Approved :: BSD License, Operating System :: POSIX :: Linux, Operating System :: Unix, Operating System :: MacOS, Operating System :: Microsoft :: Windows [entry_points] # Add here console scripts like: console_scripts = run_my_project = my_project.cli:run # as well as other entry_points. [files] # Add here 'data_files', 'packages' or 'namespace_packages'. # Additional data files are defined as key value pairs of source and target: packages = my_project data_files = share/my_project/docs = docs/* [extras] # Add here additional requirements for extra features, like: # PDF = ReportLab>=1.2, RXP ALL = django [pytest] # Options for py.test: # Specify command line options as you would do when invoking py.test directly. # e.g. --cov-report html (or xml) for html/xml output or --junitxml junit.xml # in order to write a coverage file that can be read by Jenkins. addopts = --cov my_project --cov-report term-missing --verbose [aliases] test = pytest docs = build_sphinx [bdist_wheel] # Use this option if your package is pure-python universal = 1