Use setup.cfg rather than setup.py.

[Steap]

A setup.cfg is cleaner, is easy to parse, and does not require running
any Python code. Its usage should be showcased.

[Steap]

So, setuptools >= 40.5.0 is required to use the "options.data_files" section. I wonder why it fails with the 3.5 image, and not the 2.7, 3.4 and 3.6 images. Any idea?

[dmtucker]

@Steap Maybe because 3.5 is the only version not using pip-9.0.1?

[Steap]

@dmtucker Hm, setuptools 41.0.1 seems to be installed anyway. Why would not using pip-9.0.1 be an issue?

[4383]

Duplicated with #57 maybe we can find a way to introduce these changes together by merging delta between your changes and mine.

I've propose these changes too early.

[Gadgetoid]

If you were to build a wheel from project such as this from source, with an older version of setuptools installed then it would quietly, and happily output UNKNOWN-0.0.0-py2-none-any.whl

Since there are releases of Raspbian on the Pi that ship very old setuptools packages, I'm adopting a pattern like the below to catch that edge case. I wonder if it fits here too?

from setuptools import setup, __version__
from pkg_resources import parse_version

minimum_version = parse_version('30.4.0')

if parse_version(__version__) < minimum_version:
    raise RuntimeError("Package setuptools must be at least version {}".format(minimum_version))

setup(
    install_requires=['setuptools>={}'.format(minimum_version)]
)

Note - updated code snippet with tweaks/fix from pimoroni/boilerplate-python@0060d76

[jaraco]

You definitely don't want install_requires declared there. In fact, that might interfere with install_requires declared in setup.cfg. I do think it may be worthwhile to fail fast when setuptools 30.4 isn't present.