[Python-ideas] Re: Allowing non-ASCII bracket and quote characters in source code

2022-01-20 Thread Brendan Barnwell
On 2022-01-20 23:08, Greg Ewing wrote: On 20/01/22 12:52 pm, Christopher Barker wrote: >On Wed, Jan 19, 2022 at 2:12 PM Greg Ewing > wrote: > > Those particular brackets are really confusing because they're half > square and half round. > >And THAT is

[Python-ideas] Re: Allowing non-ASCII bracket and quote characters in source code

2022-01-20 Thread Greg Ewing
On 20/01/22 12:52 pm, Christopher Barker wrote: On Wed, Jan 19, 2022 at 2:12 PM Greg Ewing > wrote: Those particular brackets are really confusing because they're half square and half round. And THAT is why this is a bad idea. It doesn't mean

[Python-ideas] Re: Allowing non-ASCII bracket and quote characters in source code

2022-01-19 Thread Christopher Barker
On Wed, Jan 19, 2022 at 2:12 PM Greg Ewing wrote: > Those particular brackets are really confusing because they're half > square and half round. And THAT is why this is a bad idea. Frankly, depending on the font and the screen and my bad old eyes, it’s hard enough to tell the three brackets

[Python-ideas] Re: Allowing non-ASCII bracket and quote characters in source code

2022-01-19 Thread Greg Ewing
On 20/01/22 3:45 am, Alexandre Brault wrote: On 2022-01-18 6:12 p.m., Chris Angelico wrote: 3) Optional semantic difference: 【1, 2, 3】 is exactly the same as (1, 2, 3), but 【1, 2, 3) would be an error. What does it say about the viability of this idea that until the second part of that

[Python-ideas] Re: Allowing non-ASCII bracket and quote characters in source code

2022-01-19 Thread Chris Angelico
On Thu, Jan 20, 2022 at 1:47 AM Alexandre Brault wrote: > > On 2022-01-18 6:12 p.m., Chris Angelico wrote: > > 3) Optional semantic difference: 【1, 2, 3】 is exactly the same as (1, > > 2, 3), but 【1, 2, 3) would be an error. > > What does it say about the viability of this idea that until the

[Python-ideas] Re: Allowing non-ASCII bracket and quote characters in source code

2022-01-19 Thread Alexandre Brault
On 2022-01-18 6:12 p.m., Chris Angelico wrote: 3) Optional semantic difference: 【1, 2, 3】 is exactly the same as (1, 2, 3), but 【1, 2, 3) would be an error. What does it say about the viability of this idea that until the second part of that sentence, I thought it would be equivalent to [1,

[Python-ideas] Re: Allowing non-ASCII bracket and quote characters in source code

2022-01-19 Thread Stephen J. Turnbull
Steven D'Aprano writes: > > Here's a better challenge: Type five unique open parenthesis signs, > > without looking up their key sequences or codepoints. > > Yes :-) Asa meshi mae (and if you know what that means -- the White Queen does -- you also know why this is trivial): ([{(〔[{〈《【

[Python-ideas] Re: Allowing non-ASCII bracket and quote characters in source code

2022-01-18 Thread MRAB
On 2022-01-19 00:02, Steven D'Aprano wrote: On Wed, Jan 19, 2022 at 10:12:23AM +1100, Chris Angelico wrote: Not sure about Python, but C and C++ have digraphs and trigraphs as alternatives for certain symbols, specifically because some OS/keyboard/language combinations may not be able to

[Python-ideas] Re: Allowing non-ASCII bracket and quote characters in source code

2022-01-18 Thread Chris Angelico
On Wed, Jan 19, 2022 at 11:10 AM Steven D'Aprano wrote: > > On Wed, Jan 19, 2022 at 10:12:23AM +1100, Chris Angelico wrote: > > > Not sure about Python, but C and C++ have digraphs and trigraphs as > > alternatives for certain symbols, specifically because some > > OS/keyboard/language

[Python-ideas] Re: Allowing non-ASCII bracket and quote characters in source code

2022-01-18 Thread Steven D'Aprano
On Wed, Jan 19, 2022 at 10:12:23AM +1100, Chris Angelico wrote: > Not sure about Python, but C and C++ have digraphs and trigraphs as > alternatives for certain symbols, specifically because some > OS/keyboard/language combinations may not be able to easily type the > originals. I believe that

[Python-ideas] Re: Allowing non-ASCII bracket and quote characters in source code

2022-01-18 Thread David Mertz, Ph.D.
On Tue, Jan 18, 2022, 5:46 PM Steven D'Aprano > Okay. Without looking it up, how would *you* type ⟮ U+27EE "Mathematical > Left Flattened Parentheses"? On your honour now, don't look it up. > You've kind of given away the game. I'd press "shift-ctrl-u 2 7 e e ". I'm not even at my computer, but

[Python-ideas] Re: Allowing non-ASCII bracket and quote characters in source code

2022-01-18 Thread Chris Angelico
On Wed, Jan 19, 2022 at 9:47 AM Steven D'Aprano wrote: > > On Tue, Jan 18, 2022 at 07:40:40AM -0700, 2qdxy4rzwzuui...@potatochowder.com > wrote: > > On 2022-01-18 at 12:07:15 +1100, > > Steven D'Aprano wrote: > > > > > I would be more sympathetic to this idea if: > > > > > 1. I knew how to

[Python-ideas] Re: Allowing non-ASCII bracket and quote characters in source code

2022-01-18 Thread Steven D'Aprano
On Tue, Jan 18, 2022 at 07:40:40AM -0700, 2qdxy4rzwzuui...@potatochowder.com wrote: > On 2022-01-18 at 12:07:15 +1100, > Steven D'Aprano wrote: > > > I would be more sympathetic to this idea if: > > > 1. I knew how to easily type all those brackets on the keyboard, > > without having to use a

[Python-ideas] Re: Allowing non-ASCII bracket and quote characters in source code

2022-01-18 Thread John Sturdy
On Tue, Jan 18, 2022 at 1:15 AM Steven D'Aprano wrote: > I would be more sympathetic to this idea if: > > 2. I had a guarantee that all of the bracket characters would be both > available and easily distinguishable in any typeface I used. > I don't think the "distinguishable" part matters that

[Python-ideas] Re: Allowing non-ASCII bracket and quote characters in source code

2022-01-18 Thread 2QdxY4RzWzUUiLuE
On 2022-01-18 at 12:07:15 +1100, Steven D'Aprano wrote: > I would be more sympathetic to this idea if: > 1. I knew how to easily type all those brackets on the keyboard, > without having to use a GUI character picker. That's between you and your OS. I believe all the major ones have ways to

[Python-ideas] Re: Allowing non-ASCII bracket and quote characters in source code

2022-01-17 Thread David Lowry-Duda
On Mon, Jan 17, 2022 at 03:27:33PM -0500, David Mertz, Ph.D. wrote: > Here's a better idea: Use parens for all the levels of nesting, as > currently, but convince your editor to substitute various other bracket-ish > things for levels of nesting. This is approximately what I do, except that I use

[Python-ideas] Re: Allowing non-ASCII bracket and quote characters in source code

2022-01-17 Thread Steven D'Aprano
I would be more sympathetic to this idea if: 1. I knew how to easily type all those brackets on the keyboard, without having to use a GUI character picker. 2. I had a guarantee that all of the bracket characters would be both available and easily distinguishable in any typeface I used.

[Python-ideas] Re: Allowing non-ASCII bracket and quote characters in source code

2022-01-17 Thread Jonathan Goble
On Mon, Jan 17, 2022 at 3:22 PM John Sturdy wrote: > But it might be handled better in the display in editors and IDEs (perhaps > syntax coloring brackets by their depth). > VSCode already supports this out of the box. Just search "bracket pair" in the settings and check (tick) the box for