On Wed, Jun 24, 2015 at 9:48 PM, Stefan Behnel <stefan_ml at behnel.de> wrote: > > > I'd wait with that a bit, though, until after Py3.5 is finally released > and the actual needs for C code that want to use the new > features become clearer. > I strongly disagree. What we would end up with is 3rd party extension modules developed over the next 2-3 years including their own awaitable testing functions/macros, and in order to continue to provide 3.5 support into the future that code will persist for the next 5-10 years regardless to whether its later added in Python 3.6. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20150625/c061fdfa/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