variable ``future.utils.PY3`` -- is time bomb

[antonov-impulsm]

issue same as in six-project: https://bitbucket.org/gutworth/six/issues/22/variable-sixpy3-is-time-bomb ..

(same as in six-project you may mark this issue as wontfix . but , ok i warned about this issue )

[polymorphm]

see this file as a good pattern -- https://github.com/python/cpython/blob/3.6/Lib/asyncio/compat.py

[benjaoming]

Following that logic, six.PY2 should be PY2 = sys.version_info[0] >= 2 ?? :)

Pretty sure this can just be closed.

[polymorphm]

Following that logic, six.PY2 should be PY2 = sys.version_info[0] >= 2 ??

yes. exactly.

but variable PY2 for six/python-future is not needed -- if variable PY3 exists.

Pretty sure this can just be closed.

of course you can. when time-bomb will explode -- I just will reopen this issue-ticket :-)

[jmadler]

I've adjusted some of the conditionals, but this is not sufficient for Py4.0 support. We'll cross that bridge once it's laid down...