#Cfg do fallen 2019 install
#Cfg do fallen 2019 update
#Cfg do fallen 2019 code

# This enables setuptools to install wheel on-the-fly SETUP_REQUIRES += if 'bdist_wheel' in sys. #!/usr/bin/env python import sys from setuptools import setup import versioneer # Give setuptools a hint to complain if it's too old a version # 30.3.0 allows us to put most metadata in setup.cfg # Should match pyproject.toml SETUP_REQUIRES = The dynamic components of my package setup are as follows: I recommend not placing the version in setup.cfg. Packages = find: replaces the find_packages() option often used in setup.py.ДЇinally, interpolated strings are used in extras_require to provide a meta-extra like all. For example, long_description = file: allows you to placeДЄ long description in a separate file, to be included in your documentation. In addition to plain key-value pairs, there are some constrained options for commonДynamic metadata.

#Cfg do fallen 2019 update

Versions - update the python_requires to avoid breaking downstream tools that still I want to draw attention to the python_requires metadata which will prevent pip fromДЄttempting to install on incompatible systems. Long_description_content_type = text/x-rst charset=UTF-8 license = GPL pyproject.tomlДЄ bare minimum pyproject.toml is as follows: Using setup.cfg to declare as much of the metadata as possible, along with pyproject.toml I have settled on a setuptools-based approach, String, and setting the version should be done from a version control tag if possible.ДЄssuming a git repository, the following should also work: To operationalize (3), all of the above should produce an install with the same version This also means that newer, better build systems that do not rely on setuptools are not python setup.py bdist_wheel & pip install dist/*.whlДЄnd development/editable mode should work:.python setup.py sdist & pip install dist/*.tar.gz.To operationalize (1), the following approaches should all install correctly: (Partially redundant with limiting dynamic metadata.)

#Cfg do fallen 2019 code

Limit custom code to absolute minimum.Enable revision-based versions, with minimal opportunity for error.Prefer declarative syntax, and limit dynamic metadata, as much as possible.Installation should work, from source, on fairly old systems.Motivating my recommendations are a few desiderata, in rough order of importance: Infrastructure I hope to stop thinking about so much. Today and where things appear to be heading, as I look to prepare or update packaging So my perspective is less concerned with what packaging should become, and more with what works Searches to identify the current state of the art. I have not followed deep arguments, but have relied mostly on PEPs, documentation and sporadic NiBabel and do a reasonable amount of maintenance work I am most active with the NIPY collection of projects, generally related My position in the Python ecosystem will color my perspective and approach to packaging,ДЄnd, presumably, how much weight you give what I think. A very small setup.py for dynamic metadata and to tie everything together.For all static (and some dynamic-ish) metadata, use.

For describing your build requirements, use.If you cite this as a justification for your behavior, please stop This document should be superseded or disregarded no later than the As of this writing Python 2.7 and Python 3.5 still have not This document has been superseded as of July 2020. Practices, but they fit my needs, and might fit yours. This document lays out a set of Python packaging practices.