On Thu, Nov 7, 2019, at 22:19, yejus...@163.com wrote:
> (1) Keeping the original syntax of List unchanged，for example：
> a = [1,2,3] # will be parsed to a normal list.
> b = [[1,2,3],[4,5,6]] # will be parsed to a normal list，too.
> Simply put, all the original list syntax remains
These thousands of words of repeating claims with weird non sequitur
digressions seem to amount to "I wish Python used hard-to-enter unicode
characters instead of words on normal keyboards" as far as I can tell
because human brains, apparently, cannot make sense of the two character
symbol `:=`
On Nov 10, 2019, at 20:50, Martin Euredjian via Python-ideas
wrote:
>
> > This has nothing to do with representation or input via text
>
> It does, it's an extension of the reality that, after so many decades, we are
> still typing words on a text editor.
And how else would you want to enter
Martin,
I think one thing you need to realize that just being a better idea
doesn't make it easy to get implemented. There is a LOT of inertia in
infrastructure, and overcoming it can be nearly impossible.
A great example of that is look at your typical keyboard, if you were to
create a new keybo
> This has nothing to do with representation or input via text
It does, it's an extension of the reality that, after so many decades, we are
still typing words on a text editor. In other words, my comment isn't so much
about the mechanics and editors that are available as much as the fact that
numpy already has a MATLAB-like sting parsing matrix creating function,
buried in the "Matrix" class:
In [1]: import numpy as np
In [2]: np.mat('1 2 3; 4 5 6')
Out[2]:
matrix([[1, 2, 3],
[4, 5, 6]])
That gives you a Matrix, not an array, butyou could wrap it in a little
utility to con
Just my opinion, I do not think this belongs in PEP8 or official guidelines.
Different editors will vary, of course, in how they handle "invisible"
characters. But since various people will read your code, I think it's
generally friendlier to use a name or Unicode escape rather than a quoted
liter
Welcome!
I would just define a module level constant that uses a Unicode escape
sequence. The code is self-documenting, and doesn’t require the runtime
overhead of the chr function:
ZERO_WIDTH_SPACE = "\u200b"
I personally don’t think this is a common/important enough case to be
documented an
> On 10 Nov 2019, at 02:22, Artemis wrote:
>
> What should one do when one wants to put a zero width space or other
> invisible character in code?
> These are often not displayed in editors, which can lead to confusion. I see
> two solutions:
> - include it but add a comment noting it
> -
What should one do when one wants to put a zero width space or other invisible
character in code?
These are often not displayed in editors, which can lead to confusion. I see
two solutions:
- include it but add a comment noting it
- use the chr function to get the character (and add a comment
On Nov 10, 2019, at 08:23, Stephen J. Turnbull
wrote:
>
> Martin Euredjian via Python-ideas writes:
>
>> Another interesting example is had in some of my work with real
>> time embedded systems. There are plenty of cases where you are
>> doing things that are very tightly related to, for examp
On Nov 10, 2019, at 08:00, Stephen J. Turnbull
wrote:
>
> Andrew Barnert via Python-ideas writes:
>>> On Nov 7, 2019, at 19:59, Chris Angelico wrote:
>>>
>>> And I do the same with the operators that you disparagingly call
>>> "ASCII soup". I touch type them. What's the difference, other than
12 matches
Mail list logo
