error in install_requires

Clean git checkout, execute python setup.py bdist_rpm

python --version: Python 2.7.5

error in asana setup command: ‘install_requires’ must be a string or list of strings containing valid project/version requirement specifiers

I also receive this message when I try to pip install the package.

If I remove the parts after the first comma, the rpm builds:

diff --git a/setup.py b/setup.py
index 6adedd7..a1d2ce3 100755
--- a/setup.py
+++ b/setup.py
@@ -26,9 +26,9 @@ setup(
         'Programming Language :: Python :: 3.4'
     ],
     install_requires=[
-        'requests >=2.14.2, == 2.14.*',
-        'requests_oauthlib >= 0.6.1, == 0.6.*',
-        'six >= 1.10.0, == 1.10.*'
+        'requests >=2.14.2',
+        'requests_oauthlib >= 0.6.1',
+        'six >= 1.10.0'
     ],
     author='Asana, Inc',
     # author_email='',

┆Issue is synchronized with this Asana task

[praecipula]

This is interesting because the current version specifier string was an attempt to keep our library compatible to older versions of setuptools that didn’t yet follow the compatible release version specifier of ~=. If you follow that link, you’ll see that the current strings are meant to be the “semantic meaning” that they suggest for an equivalent of ~=, but it’d be a shame if that doesn’t actually work.

This is tricky to test because we’d have to set up a machine / VM image with its configuration to be just right to test it out. In any case, newer versions of setuptools after version 8.0 (Dec 2014) should have no problem with either way of specifying a compatible release.

Could you attach the output of what your machine says when you run

pip show setuptools | grep Version

If it appears to be greater than 8.0, we’ll have to dig in deeper.

Otherwise, you should be able to get moving by running

pip install --upgrade setuptools

If that doesn’t work, be sure to let us know!

[theaeolianmachine]

We recently cut a new release of v0.6.7 - feel free to try it out using a version of setuptools greater than 8.0, and let us know if you run into any issues!