You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
@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.
Activity
Docs: FAQ: Mention issue #29 as the place for requesting Python 3.2 s…
edschofield commentedon Jan 13, 2014
@pboehm: Thanks for mentioning this. Python 3.2 was released before PEP 414 was ratified, so
futurecurrently 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
futurewould likely impose a penalty with performance and/or maintainability, so we would only do this if there were significant demand.pboehm commentedon Jan 13, 2014
Okay sounds reasonable. I have excluded 3.2 from testing ...
[-]SyntaxError in utils/__init__.py on Python 3.2[/-][+]Request for Python 3.2 support[/+]davidak commentedon May 22, 2016
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)
jmadler commentedon Sep 10, 2018
Py3.2 is now EOL, and this request is a bit dated. Closing! :)