[Python-ideas] Re: foo.setParseAction(lambda a, b, c: raise FuckPython(":("))

2019-11-05 Thread Random832
On Sun, Nov 3, 2019, at 11:01, Andrew Barnert via Python-ideas wrote: > > counter-argument: foo = raise NIY > > What is that a counter-argument to? The fact that it would nearly > always be completely useless to assign a raise? > > I don’t know what NIY means here, but why couldn’t you write thi

[Python-ideas] Re: foo.setParseAction(lambda a, b, c: raise FuckPython(":("))

2019-11-05 Thread Greg Ewing
Random832 wrote: I have, occasionally, wanted to be able to resume a function after handling an exception ... In a hypothetical implementation that would allow such a thing, having the raise return a value in such a scenario might not be unreasonable. For that to be of any use, the code that ra

[Python-ideas] Re: foo.setParseAction(lambda a, b, c: raise FuckPython(":("))

2019-11-05 Thread Random832
On Tue, Nov 5, 2019, at 16:22, Greg Ewing wrote: > Random832 wrote: > > I have, occasionally, wanted to be able to resume a function > > after handling an exception ... In a hypothetical > > implementation that would allow such a thing, having the raise return a > > value > > in such a scenario mi

[Python-ideas] Re: foo.setParseAction(lambda a, b, c: raise FuckPython(":("))

2019-11-05 Thread Andrew Barnert via Python-ideas
On Nov 5, 2019, at 21:48, Random832 wrote: > > As a side note, I have, occasionally, wanted to be able to resume a function > after handling an exception (the use case was to turn a synchronous outer > function calling an asynchronous callback into an asynchronous function), > which - needless

[Python-ideas] Python should take a lesson from APL: Walrus operator not needed

2019-11-05 Thread martin_05--- via Python-ideas
During a recent HN discussion about the walrus operator I came to realize yet another advantage of notation. I used APL professionally for about ten years, which made it an obvious source of inspiration for an example that, in my opinion, demonstrates why the Python team missed a very valuable o

[Python-ideas] Re: Python should take a lesson from APL: Walrus operator not needed

2019-11-05 Thread Chris Angelico
On Wed, Nov 6, 2019 at 3:28 PM martin_05--- via Python-ideas wrote: > Back to Python. > > This entire mess could have been avoided by making one simple change that > would have possibly nudged the language towards a very interesting era, one > where a specialized programming notation could be ev

[Python-ideas] Re: Python should take a lesson from APL: Walrus operator not needed

2019-11-05 Thread Greg Ewing
martin_05--- via Python-ideas wrote: The transition to only allowing "←" (and perhaps other symbols) could be planned for Python 4. Requiring non-ascii characters in the core language would be a very big change, especially for something as ubiquitous as assignment. Much more justification than

[Python-ideas] Re: Python should take a lesson from APL: Walrus operator not needed

2019-11-05 Thread Alex Walters
The arrow ...which I will not copy and paste to really hammer home the point that its not on my fairly standard US keyboard... doesn't look like assignment, it looks like a comparison operator. > -Original Message- > From: martin_05--- via Python-ideas > Sent: Tuesday, November 5, 2019

[Python-ideas] Re: Python should take a lesson from APL: Walrus operator not needed

2019-11-05 Thread Richard Musil
On Wed, Nov 6, 2019 at 5:32 AM martin_05--- via Python-ideas < python-ideas@python.org> wrote: > In other words, these two things would have been equivalent in Python: > > a ← 23 > > a = 23 > I do not consider these two things conceptually equivalent. In Python the identifier ('a' in this