I've come across this amazing library and found a possible bug on Python 3.2. I found this in a django extension which is tested by Travis against 2.7, 3.2 and 3.3 and on 3.2 the tests fail because of an SyntaxError in future/utils/init.py.
Traceback (most recent call last):
File "/home/travis/virtualenv/python3.2/lib/python3.2/site-packages/future/utils/__init__.py", line 419
return isinstance(obj, type(u''))
SyntaxError: invalid syntax
This only occurs on 3.2 as you can see here https://travis-ci.org/pboehm/django-data-migration/builds/16821855 . For me this looks like a weird error because I couldn't see and error in this line ...
Docs: FAQ: Mention issue #29 as the place for requesting Python 3.2 s…
@pboehm: Thanks for mentioning this. Python 3.2 was released before PEP 414 was ratified, so future currently supports Python 3.3+ only in the 3.x series. (See here.)
The FAQ now mentions this issue as the place to request support for Python 3.2. Adding support for Python 3.2 to future would likely impose a penalty with performance and/or maintainability, so we would only do this if there were significant demand.
Okay sounds reasonable. I have excluded 3.2 from testing ...
Python 3.2 is available on Ubuntu 12.04 LTS which is still supported until 2017, but 2.7 is installed by default.
Also PyPy3 is based on Python 3.2.5. (but it works)