On Monday, May 14, 2018, Ethan Furman <ethan at 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. https://github.com/python/cpython/blame/master/Lib/__future__.py > > -- > ~Ethan~ > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: https://mail.python.org/mailman/options/python-dev/wes. > turner%40gmail.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20180514/3f477702/attachment.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4