Steven D'Aprano <steve+pyt...@pearwood.info> added the comment:
You are one person, who has used this feature for what, a month elapsed
time? 300 person-hours actual experience with it? Allowing top-level
unparenthisized walrus expressions will affect hundreds of thousands of
people, for collectively millions of hours over a decade or more of
elapsed time. What's the rush about lifting this restriction?
If the restriction turns out to be "pointless", then we can remove it
later, and no harm done. You say this is ugly in the notebooks:
(variable := expression)
but it is surely still an improvement over the status quo:
variable = expression; variable
But if we remove it now, and it turns out that it wasn't as pointless as
you thought, then we're stuck with a design mistake that will be very
hard to fix without breaking people's code.
I'm glad you've found an excellent use-case for unbracketed assignment
expressions, and I don't oppose your suggested change, I'm just
advocating caution.
Besides, Jypiter already allows interactive code that would be a syntax
error outside of their environment. They can probably relax that
restriction within Jypiter, while still leaving the language alone.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue35224>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
