(original) (raw)

On Monday, May 14, 2018, Ethan Furman <ethan@stoneleaf.us> wrote:

On 05/14/2018 09:34 AM, Chris Barker via Python-Dev wrote:

between 3.0 and 3.6 (.5?) -- py3 grew a lot of minor features that made it easier to write py2/py3 compatible code.
u"string", b'bytes %i' % something -- and when where the various \_\_future\_\_ imports made available?

If these had been in place in 3.0, the whole process would have been easier :-(

You'll need to be more specific. \_\_future\_\_ has been around for a looooong time.

\--
\~Ethan\~
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: https://mail.python.org/mailman/options/python-dev/wes.turner%40gmail.com