[Python-Dev] Intricacies of calling __eq__
Antoine Pitrou
solipsis at pitrou.net
Wed Mar 19 14:17:19 CET 2014
More information about the Python-Dev mailing list
Wed Mar 19 14:17:19 CET 2014
- Previous message: [Python-Dev] Intricacies of calling __eq__
- Next message: [Python-Dev] Intricacies of calling __eq__
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, 19 Mar 2014 15:09:04 +0200 Maciej Fijalkowski <fijall at gmail.com> wrote: > > I would like to point out that instructing people does not really > work. Besides, other examples like this: > > if d[x] >= 3: > d[x] += 1 don't really work. That's a good point. But then, perhaps PyPy should analyze the __eq__ method and decide whether it's likely to have side effects or not (the answer can be hard-coded for built-in types such as str). Regards Antoine.
- Previous message: [Python-Dev] Intricacies of calling __eq__
- Next message: [Python-Dev] Intricacies of calling __eq__
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list