Re: get_used_memory

2026-06-22 Thread Antoon Pardon
Op 16/06/2026 om 14:48 schreef Chris Angelico via Python-list: On Tue, 16 Jun 2026 at 22:45, Rob Cliffe via Python-list wrote: You know what "arbitrary" means, but let's take it as "decided for no good reason". I have read the PEP and it simply states "NAME is an identifier" and l

Re: get_used_memory

2026-06-22 Thread Simon Ward
On 22/06/2026 16:35, Rob Cliffe via Python-list wrote: How much more helpful to explain *why* it won't work. So if you know of one or more things that would break if walrus targets were unrestricted, please spell (one of more of) them out. This commit to PEP 572 shows that it started out with

Re: get_used_memory

2026-06-22 Thread Chris Angelico via Python-list
On Tue, 23 Jun 2026 at 01:38, Rob Cliffe via Python-list wrote: > Chris, please can you be more helpful? > If I said "I think it's possible to square the circle with compass and > straight-edge" > and you replied "Try it; it won't work" > you would be correct, but I might waste a lifetime trying.

Re: get_used_memory

2026-06-22 Thread Rob Cliffe via Python-list
On 22/06/2026 13:42, Chris Angelico via Python-list wrote: On Mon, 22 Jun 2026 at 21:45, Antoon Pardon wrote: Sure, you replace the rule: name ':=' expression with: target ':=' expression So why shouldn't that work? I said *try it*. Don't tell me about it, try it. Actually bui

Re: get_used_memory

2026-06-22 Thread Chris Angelico via Python-list
On Mon, 22 Jun 2026 at 21:45, Antoon Pardon wrote: > Sure, you replace the rule: > > name ':=' expression > > with: > > target ':=' expression > > So why shouldn't that work? I said *try it*. Don't tell me about it, try it. Actually build Python from source with that change, and then see