[Python-Dev] PEP 492: aiter should return async iterator directly instead of awaitable (original) (raw)
Barry Warsaw barry at python.org
Mon Jun 6 16:58:54 EDT 2016
- Previous message (by thread): [Python-Dev] PEP 492: __aiter__ should return async iterator directly instead of awaitable
- Next message (by thread): [Python-Dev] Proper way to specify that a method is not defined for a type
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Jun 06, 2016, at 01:02 PM, Łukasz Langa wrote:
There’s a problem with this approach. It will force people to write deprecated code because you never know if your library is going to run on 3.5.0 or 3.5.1. Barry, Ubuntu wily, xenial and yakkety currently package 3.5.0 or 3.5.1. When 3.5.2 is going to get released, are they going to get it? I’m pretty sure wily isn’t and yakkety is but just wanted to confirm; especially with xenial being an LTS release.
Matthias and I talked briefly about this at Pycon. We want to get 3.5.2 into Ubuntu 16.04.1 if it's released in time. 16.04.1 is currently scheduled for July 21st [1] so if Larry keeps with his announced schedule that should work out[2].
Obviously it would make it into Yakkety too. It's not worth it for Wily (15.10) since that EOLs next month.
Cheers, -Barry
[1] https://wiki.ubuntu.com/XenialXerus/ReleaseSchedule [2] https://mail.python.org/pipermail/python-dev/2016-April/144383.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: <http://mail.python.org/pipermail/python-dev/attachments/20160606/4018eaf4/attachment.sig>
- Previous message (by thread): [Python-Dev] PEP 492: __aiter__ should return async iterator directly instead of awaitable
- Next message (by thread): [Python-Dev] Proper way to specify that a method is not defined for a type
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]