On Sat, Dec 19, 2015 at 9:16 AM, Marko Rauhamaa wrote:
> Terry Reedy :
>
>> Guido also wants syntax chars and identifiers in stdlib code kept to
>> ascii only for universal readability.
>
> Readability, or writability? Most people would have no idea how to
> produce the characters with their keybo
Terry Reedy :
> Guido also wants syntax chars and identifiers in stdlib code kept to
> ascii only for universal readability.
Readability, or writability? Most people would have no idea how to
produce the characters with their keyboards.
Marko
--
https://mail.python.org/mailman/listinfo/python-
On 12/18/2015 4:49 AM, Steven D'Aprano wrote:
On Fri, 18 Dec 2015 05:51 pm, Chris Angelico wrote:
I would be inclined to ASCIIfy the apostrophes, dashes, and the
connection.py space that started this thread. People's names, URLs,
and demonstrative characters I'm more inclined to leave. Agreed?
On Fri, Dec 18, 2015 at 3:51 AM, Steven D'Aprano wrote:
> On Fri, 18 Dec 2015 11:02 am, Mark Lawrence wrote:
>
>> A lot of it is down to Windows, as the actual complaint is:-
>>
>> six.print_(source)
>
> Looks like a bug in six to me.
>
> See, without Unicode comments in the std lib, you neve
On Fri, 18 Dec 2015 06:12 pm, Serhiy Storchaka wrote:
> Using non-ASCII apostrophes and like in docstrings may be considered a
> bug.
Absolutely not a bug. In Python 3, docstrings are Unicode, not bytes, and
can contain any valid (or even invalid) Unicode code points, including
non-characters.
On Fri, 18 Dec 2015 11:02 am, Mark Lawrence wrote:
> A lot of it is down to Windows, as the actual complaint is:-
>
> six.print_(source)
Looks like a bug in six to me.
See, without Unicode comments in the std lib, you never would have found
that bug.
--
Steven
--
https://mail.python.o
On Fri, 18 Dec 2015 05:51 pm, Chris Angelico wrote:
> I would be inclined to ASCIIfy the apostrophes, dashes, and the
> connection.py space that started this thread. People's names, URLs,
> and demonstrative characters I'm more inclined to leave. Agreed?
No.
--
Steven
--
https://mail.pytho
On Fri, 18 Dec 2015 10:05 am, Mark Lawrence asked:
"Should stdlib files contain 'narrow non breaking space' U+202F?"
Absolutely it should.
What better way to ensure that the interpreter works correctly with Unicode
than to use Unicode in the std lib?
--
Steven
--
htt
On Fri, Dec 18, 2015 at 7:32 PM, Zachary Ware
wrote:
> On Fri, Dec 18, 2015 at 1:43 AM, Chris Angelico wrote:
>> On Fri, Dec 18, 2015 at 6:12 PM, Serhiy Storchaka
>> wrote:
>>> Agreed. Please open an issue.
>>>
>>> Using non-ASCII apostrophes and like in docstrings may be considered a bug.
>>
>
On 18.12.15 09:43, Chris Angelico wrote:
On Fri, Dec 18, 2015 at 6:12 PM, Serhiy Storchaka wrote:
Agreed. Please open an issue.
Using non-ASCII apostrophes and like in docstrings may be considered a bug.
http://bugs.python.org/issue25899
Thanks.
Also noticed this. Is this a markup error?
On Fri, Dec 18, 2015 at 1:43 AM, Chris Angelico wrote:
> On Fri, Dec 18, 2015 at 6:12 PM, Serhiy Storchaka wrote:
>> Agreed. Please open an issue.
>>
>> Using non-ASCII apostrophes and like in docstrings may be considered a bug.
>
> http://bugs.python.org/issue25899
>
> Also noticed this. Is this
On Fri, Dec 18, 2015 at 6:12 PM, Serhiy Storchaka wrote:
> Agreed. Please open an issue.
>
> Using non-ASCII apostrophes and like in docstrings may be considered a bug.
http://bugs.python.org/issue25899
Also noticed this. Is this a markup error?
Lib/urllib/request.py:190:
Note that *None& m
On Fri, Dec 18, 2015 at 6:12 PM, Serhiy Storchaka wrote:
> Agreed. Please open an issue.
>
> Using non-ASCII apostrophes and like in docstrings may be considered a bug.
http://bugs.python.org/issue25899
Also noticed this. Is this a markup error?
Lib/urllib/request.py:190:
Note that *None& m
On 18.12.15 08:51, Chris Angelico wrote:
On Fri, Dec 18, 2015 at 5:36 PM, Terry Reedy wrote:
Last I knew, Guido still wanted stdlib files to be all-ascii, especially
possibly in special cases. There is no good reason I can think of for there
to be an invisible non-ascii space in a comment. It
On Fri, Dec 18, 2015 at 5:36 PM, Terry Reedy wrote:
> Last I knew, Guido still wanted stdlib files to be all-ascii, especially
> possibly in special cases. There is no good reason I can think of for there
> to be an invisible non-ascii space in a comment. It strikes me as most
> likely an acciden
On 12/17/2015 6:18 PM, Chris Angelico wrote:
On Fri, Dec 18, 2015 at 10:05 AM, Mark Lawrence wrote:
The culprit character is hidden between "Issue #" and "20540" at line 400 of
C:\Python35\Lib\multiprocessing\connection.py.
https://bugs.python.org/issue20540 and
https://hg.python.org/cpython/re
On Fri, Dec 18, 2015 at 11:02 AM, Mark Lawrence wrote:
> A lot of it is down to Windows, as the actual complaint is:-
>
> six.print_(source)
> File "C:\Python35\lib\encodings\cp1252.py", line 19, in encode
> return codecs.charmap_encode(input,self.errors,encoding_table)[0]
> UnicodeEncod
On 17/12/2015 23:18, Chris Angelico wrote:
On Fri, Dec 18, 2015 at 10:05 AM, Mark Lawrence wrote:
The culprit character is hidden between "Issue #" and "20540" at line 400 of
C:\Python35\Lib\multiprocessing\connection.py.
https://bugs.python.org/issue20540 and
https://hg.python.org/cpython/rev/
On Fri, Dec 18, 2015 at 10:05 AM, Mark Lawrence wrote:
> The culprit character is hidden between "Issue #" and "20540" at line 400 of
> C:\Python35\Lib\multiprocessing\connection.py.
> https://bugs.python.org/issue20540 and
> https://hg.python.org/cpython/rev/125c24f47f3c refers.
>
> I'm asking as
On Thu, Dec 17, 2015 at 4:05 PM, Mark Lawrence wrote:
> The culprit character is hidden between "Issue #" and "20540" at line 400 of
> C:\Python35\Lib\multiprocessing\connection.py.
> https://bugs.python.org/issue20540 and
> https://hg.python.org/cpython/rev/125c24f47f3c refers.
>
> I'm asking as
The culprit character is hidden between "Issue #" and "20540" at line
400 of C:\Python35\Lib\multiprocessing\connection.py.
https://bugs.python.org/issue20540 and
https://hg.python.org/cpython/rev/125c24f47f3c refers.
I'm asking as I've just spent 30 minutes tracking down why my debug code
wo
21 matches
Mail list logo