[Python-Dev] PEP 492: async/await in Python; v3 (original) (raw)
Greg Ewing greg.ewing at canterbury.ac.nz
Wed Apr 29 11:12:49 CEST 2015
- Previous message (by thread): [Python-Dev] PEP 492: async/await in Python; v3
- Next message (by thread): [Python-Dev] PEP 492: async/await in Python; v3
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Guido van Rossum wrote:
There's a cost to future imports too. The current proposal is a pretty clever hack -- and we've done similar hacks in the past
There's a benefit to having a future import beyond avoiding hackery: by turning on the future you can find out what will break when they become real keywords.
But I suppose that could be achieved by having both the hack and the future import available.
-- Greg
- Previous message (by thread): [Python-Dev] PEP 492: async/await in Python; v3
- Next message (by thread): [Python-Dev] PEP 492: async/await in Python; v3
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]