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

2019-11-11 Thread Greg Ewing
On 12/11/19 4:10 am, Random832 wrote: well *of course* the goal was not to slow down actual production of text, but this does not imply the method by which "speeding up by preventing jams" was to be achieved was not by slowing down the physical process of pressing keys. That wasn't the method,

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

2019-11-11 Thread Christopher Barker
On Mon, Nov 11, 2019 at 4:16 PM David Mertz wrote: > I really, really don't get how it's supposed to "transform my thinking > about coding" to have a slightly different glyph on screen. > I agree here. This thread got really caught up in issues like "how do I type that?", but I don't think

[Python-ideas] Re: Domain Specification

2019-11-11 Thread Andrew Barnert via Python-ideas
On Nov 11, 2019, at 15:58, Chris Angelico wrote: > > I'd recommend exploring two paths: > > 1) MacroPy > 2) Preprocessors/compilers > > MacroPy is an insanely powerful tool for messing around with Python. > You may well be able to do what you want that way. If you can't, > though, what I'd

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

2019-11-11 Thread David Mertz
I implemented this discussed arrow operator in vim with conceal plugin. This is an example given in PEP 572. It looks perfectly fine. It also does not require ANY change to Python-the-language. It just means that I can type ':' followed by '=' to get that, rather than type 'Alt+Shift', '2',

[Python-ideas] Re: Domain Specification

2019-11-11 Thread Chris Angelico
On Tue, Nov 12, 2019 at 10:52 AM Abe Dillon wrote: > > Many fields develop their own specific short-hand notation and vocabulary for > communicating the complex yet recurring ideas within that field easily. In > many cases, this is a modification of an existing language or, in some cases, >

[Python-ideas] Domain Specification

2019-11-11 Thread Abe Dillon
Many fields develop their own specific short-hand notation and vocabulary for communicating the complex yet recurring ideas within that field easily. In many cases, this is a modification of an existing language or, in some cases, many different languages. This idea is a bit half-baked, but

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

2019-11-11 Thread Mike Miller
On 2019-11-10 12:50, Martin Euredjian via Python-ideas wrote: I have found that trying to explain the value of true notation to people who lack the experience and training is always a losing proposition.  I'm already regretting having started this thread, simply because I know how this works.

[Python-ideas] Re: Make itertools recipes license easier

2019-11-11 Thread Guido van Rossum
I have news from the PSF's lawyer (Van Lindberg). He writes: """ We don't need to change the Python license as long as all contributors have signed the CLA. Our CLA text actually allows us to relicense contributions under any open source license approved by the board. That means that we can have

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

2019-11-11 Thread C. Titus Brown
Hi folks, moderator here. I’d (strongly) suggest no further replies, unless there’s something Python specific to discuss. I’ll put the list into emergency moderation for a bit. thanks, —titus > On Nov 11, 2019, at 9:05 AM, Ricky Teachey wrote: > > > I have found that trying to explain the

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

2019-11-11 Thread Ricky Teachey
> I have found that trying to explain the value of true notation to people > who lack the experience and training is always a losing proposition. I'm > already regretting having started this thread, simply because I know how > this works. Frankly, it's almost like trying to engage with a

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

2019-11-11 Thread Martin Euredjian via Python-ideas
> These thousands of words of repeating claims with weird non sequitur > digressions seem to amount to I am done with this thread.  It has received nothing but close-minded hostility.  Which is fine.  I understand.  That's the way the world works.  I've seen this kind of thing happen in

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

2019-11-11 Thread Anders Hovmöller
> On 11 Nov 2019, at 17:05, Richard Damon wrote: > > On 11/11/19 10:10 AM, Random832 wrote: >>> On Mon, Nov 11, 2019, at 03:22, Greg Ewing wrote: >>> On 11/11/19, 12:41 PM, Richard Damon wrote: it was DESIGNED to be inefficient (that was one of its design goals, to slow typesetters

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

2019-11-11 Thread Richard Damon
On 11/11/19 10:10 AM, Random832 wrote: > On Mon, Nov 11, 2019, at 03:22, Greg Ewing wrote: >> On 11/11/19, 12:41 PM, Richard Damon wrote: >>> it was DESIGNED to be inefficient (that was one of its design goals, to >>> slow typesetters down to be slower than the machine they were working >>> on).

[Python-ideas] Re: A bit change to create a matrix variable in Python as easy as MATLAB and Julia!

2019-11-11 Thread Andrew Barnert via Python-ideas
On Nov 11, 2019, at 04:11, Random832 wrote: > > Possible alternate mechanisms: > > Make any such expression implicitly call a special function named e.g. > __matrixhook__ > - called by name, so a default in builtins and one could be set locally in a > module or imported from numpy > - or