Closed masojus closed 7 years ago
I think this issue and corresponding change probably just made it into the travis image and that's what broke us. Seems like an option is to install setuptools < 30.
This change will fix the failure by installing setuptools<30 for Python 3.2 if we decide to continue support: https://github.com/keenlabs/KeenClient-Python/commit/9c16734d34773910a1935f203b33f50b800e76ae
Thanks @baumatron! I'll keep it for now and open a bug so we can have a larger discussion about 3.2 support.
I incorporated @baumatron's change with 6befef0 so 3.2 testing is alive as it stands today. Closing this Issue.
On 4/18/17, against commit 476c00f, the 3.2 job worked just fine:
...but then with no changes, on 5/16/17, against commit 6a13679, the 3.2 job failed while installing
pycryptodome
:There is also a new note from Travis that says this environment changed in this timeframe:
This job ran on our Precise, sudo: required environment which was updated on May 4th. Please check our blog for more details about this update.
The blog entry is here in case that turns out to be pertinent.I tried changing pip versions on the fly and using different versions of
pycryptodome
and such, to no avail. In the meantime, we'll have to remove 3.2 from the list of Python versions we test against, and revisit this down the road.