setuptools_scm.version.SetuptoolsOutdatedWarning: your setuptools is too old

Hi there!

We’ve seen the following reported in Molecule (over in https://github.com/ansible/molecule/issues/1859#issue-423669576):

$ pip install --user molecule
[...]
Collecting testinfra==1.19.0 (from molecule==2.20)
  Using cached https://files.pythonhosted.org/packages/2b/96/3c0eb74894acf3e026e437ee1b1161a200adb9c9a189c36bc4a92ed2db79/testinfra-1.19.0.tar.gz
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-build-asndpD/testinfra/setup.py", line 59, in <module>
        'six>=1.4',
      File "/usr/lib64/python2.7/distutils/core.py", line 112, in setup
        _setup_distribution = dist = klass(attrs)
      File "/usr/lib/python2.7/site-packages/setuptools/dist.py", line 269, in __init__
        _Distribution.__init__(self,attrs)
      File "/usr/lib64/python2.7/distutils/dist.py", line 287, in __init__
        self.finalize_options()
      File "/usr/lib/python2.7/site-packages/setuptools/dist.py", line 302, in finalize_options
        ep.load()(self, ep.name, value)
      File "/tmp/pip-build-asndpD/testinfra/setuptools_scm-3.2.0-py2.7.egg/setuptools_scm/integration.py", line 10, in version_keyword
      File "/tmp/pip-build-asndpD/testinfra/setuptools_scm-3.2.0-py2.7.egg/setuptools_scm/version.py", line 66, in _warn_if_setuptools_outdated
    setuptools_scm.version.SetuptoolsOutdatedWarning: your setuptools is too old (<12)

The comment in https://github.com/ansible/molecule/issues/1859#issuecomment-475332782 (slightly irate but well meaning, hope you understand 😃) that argued for a fix over here in testinfra. It hinted at a solution where we could avoid setuptools being involved in the install process completely (I defer to @webknjaz at what that solution looks like).

If we’re coming to an agreement, I have some time to commit for the fix.

Thanks for the good work here.

[ssbarnea]

When read this thread few hours ago I was ready to reply right away but I am glad I didn’t because I was bit “negatively loaded”.

I invite everyone involved in this to take break, let this rest a bit and look again in a couple of days and try to find common grounds, solutions.

Most of us do open-source contributions in our free time, regardless who is employing us. Lets thing about ways of doing things that do not break others workflows. Or at least when this happens by mistake, lets work togheter in finding solutions.

[philpep]

… creaking door …

I uploaded wheels for testinfra 2.0.0 and 1.19.0 (the version pinned by molecule), which should fix installation of molecule/testinfra bypassing systems shipping old setuptools.

slam