[issue39154] "utf8" not always a synonym for "utf-8" in lib2to3

2021-10-20 Thread Irit Katriel
Change by Irit Katriel : -- resolution: -> wont fix stage: test needed -> resolved status: open -> closed ___ Python tracker ___

[issue39154] "utf8" not always a synonym for "utf-8" in lib2to3

2020-01-09 Thread STINNER Victor
Change by STINNER Victor : -- nosy: -vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39154] "utf8" not always a synonym for "utf-8" in lib2to3

2020-01-03 Thread Terry J. Reedy
Change by Terry J. Reedy : -- nosy: +benjamin.peterson stage: -> test needed versions: +Python 3.9 -Python 3.6 ___ Python tracker ___

[issue39154] "utf8" not always a synonym for "utf-8" in lib2to3

2019-12-29 Thread Peter Ludemann
Peter Ludemann added the comment: To clarify and fix a typo ... lib2to3.pgen2.tokenize.detect_encoding checks for 'utf-8'(and 'utf_8') but not 'utf8' in various places. Similarly for 'latin-1' and 'latin1'. (The codecs documentation page allows 'utf8' and 'latin1' as codecs.) ['UTF-8' is

[issue39154] "utf8" not always a synonym for "utf-8" in lib2to3

2019-12-29 Thread Ned Deily
Change by Ned Deily : -- Removed message: https://bugs.python.org/msg358997 ___ Python tracker ___ ___ Python-bugs-list mailing

[issue39154] "utf8" not always a synonym for "utf-8" in lib2to3

2019-12-29 Thread Ned Deily
Change by Ned Deily : -- Removed message: https://bugs.python.org/msg358994 ___ Python tracker ___ ___ Python-bugs-list mailing

[issue39154] "utf8" not always a synonym for "utf-8" in lib2to3

2019-12-29 Thread Peter Ludemann
Peter Ludemann added the comment: (oops -- updated this bug instead of submitting a new one) See also https://bugs.python.org/issue39155 -- ___ Python tracker ___

[issue39154] "utf8" not always a synonym for "utf-8" in lib2to3

2019-12-29 Thread Peter Ludemann
Peter Ludemann added the comment: lib2to3.tokenize should allow 'utf8' and 'utf-8' interchangeably, to be consistent with the rest of the Python library (I looked through the library source, and there seems to be no consistent preference, and also many (but not all) checks for 'utf-8' also