[Python-Dev] async __setitem__
Guido van Rossum
guido at python.org
Sun Jun 21 11:08:00 CEST 2015
More information about the Python-Dev mailing list
Sun Jun 21 11:08:00 CEST 2015
- Previous message (by thread): [Python-Dev] async __setitem__
- Next message (by thread): [Python-Dev] async __setitem__
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sun, Jun 21, 2015 at 12:48 AM, Greg Ewing <greg.ewing at canterbury.ac.nz> wrote: > Nick Coghlan wrote: > >> What if we're assigning to >> multiple targets, do the run in parallel? How is tuple unpacking >> handled? How is augmented assignment handled? >> >> If we allow asynchronous assignment, do we allow asynchronous deletion as >> well? >> > > Yeah, we'd kind of be letting the camel's nose in > here. There's no obvious place to stop until *every* > dunder method has an async counterpart. Exactly. We should not go here at all. -- --Guido van Rossum (python.org/~guido) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20150621/32259fbb/attachment.html>
- Previous message (by thread): [Python-Dev] async __setitem__
- Next message (by thread): [Python-Dev] async __setitem__
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list