Mark Dickinson <dicki...@gmail.com> added the comment:
> At least for optimization, IMHO it worth taking the shot.
For me, this feels a bit backwards: IMO you should decide what behaviour you
want first, implement the desired behaviour, and then optimize (if possible)
while keeping that same desired behaviour. It's rare that we want an
optimization to drive behaviour changes.
So for me, the key question that needs answering is: independent of any
performance changes, do we want the behaviour change? Specifically, do we want
something like "d = {}; d[1:2] = True" to "work" in Python 3.10, given that in
previous releases it raises TypeError? What are the potential benefits or
drawbacks for the user?
If you can get consensus that the behaviour change is fine, then by all means
go ahead with the optimization. But I think the behaviour question needs to be
answered first.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue42454>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
