Walrus operator variable leaking is fine for global use, but even when the walrus operator variable in the list comprehensions also leaking to globals is acceptable?
Should we not report it as a bug for it
[(t:=(t, sum(t)) if i else (0,1)) for i in range(20)]
[0, 1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89, 144, 233, 377, 610, 987, 1597, 2584, 4181]
In the above example the t variable is leaking into the global-namespace
Even when in the list-comprehension. Is the design of walrus operator is such that it can be accessible in the global-namespace or should the implementation with list-comprehensions should change such that the variable does not leaks in globals namespace should we open an issue for this