[issue215907] Encoding of "=" by quopri.py module

Change by admin : ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue525439] tcl: encoding not found

Change by admin : -- github: None -> 36194 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue509117] encoding error when joining path

Change by admin : -- github: None -> 35985 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue423221] Add a few Windows encoding aliases

Change by admin : -- github: None -> 34492 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue432401] unicode encoding error callbacks

Change by admin : -- github: None -> 34615 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue215712] mimetools.decode doesn't work with '7bit' encoding

Change by admin : ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue212265] Impossible to get Win32 default font encoding in Tk widgets

Change by admin : ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue215907] Encoding of "=" by quopri.py module

Change by admin : -- github: None -> 33259 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue215712] mimetools.decode doesn't work with '7bit' encoding

Change by admin : -- github: None -> 33244 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue212265] Impossible to get Win32 default font encoding in Tk widgets

Change by admin : -- github: None -> 32955 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue47000] Make encoding="locale" uses locale encoding even in UTF-8 mode is enabled.

Inada Naoki added the comment: New changeset 4216dce04b7d3f329beaaafc82a77c4ac6cf4d57 by Inada Naoki in branch 'main': bpo-47000: Make `io.text_encoding()` respects UTF-8 mode (GH-32003) https://github.com/python/cpython/commit/4216dce04b7d3f329beaaafc82a77c4ac6cf4d57 --

[issue24563] [doc] Encoding declaration: doc supported encodings

Change by Terry J. Reedy : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue24563] [doc] Encoding declaration: doc supported encodings

miss-islington added the comment: New changeset ce6af314ca8529d5ed0f307deb9c33029a69f4cb by Miss Islington (bot) in branch '3.10': bpo-24563: Link encoding names to encoding declarations (GH-32274) https://github.com/python/cpython/commit/ce6af314ca8529d5ed0f307deb9c33029a69f4cb

[issue24563] [doc] Encoding declaration: doc supported encodings

miss-islington added the comment: New changeset f4e280d8c5461fa5e928fa07f6cd1779a4ac43ba by Miss Islington (bot) in branch '3.9': bpo-24563: Link encoding names to encoding declarations (GH-32274) https://github.com/python/cpython/commit/f4e280d8c5461fa5e928fa07f6cd1779a4ac43ba

[issue24563] [doc] Encoding declaration: doc supported encodings

Change by miss-islington : -- pull_requests: +30339 pull_request: https://github.com/python/cpython/pull/32276 ___ Python tracker ___

[issue24563] [doc] Encoding declaration: doc supported encodings

Change by miss-islington : -- nosy: +miss-islington nosy_count: 4.0 -> 5.0 pull_requests: +30338 pull_request: https://github.com/python/cpython/pull/32275 ___ Python tracker

[issue24563] [doc] Encoding declaration: doc supported encodings

Terry J. Reedy added the comment: New changeset 01be5d6446abbdd95d0c18bd19a58a62b05568d8 by Terry Jan Reedy in branch 'main': bpo-24563: Link encoding names to encoding declarations (GH-32274) https://github.com/python/cpython/commit/01be5d6446abbdd95d0c18bd19a58a62b05568d8

[issue24563] [doc] Encoding declaration: doc supported encodings

Change by Terry J. Reedy : -- pull_requests: +30337 pull_request: https://github.com/python/cpython/pull/32274 ___ Python tracker ___

[issue24563] [doc] Encoding declaration: doc supported encodings

Terry J. Reedy added the comment: I am writing a PR with an internal link. I decided that linking to Standard Encodings is sufficient. The Python Text Encodings section follows that. Anyone wanting to use any of those can experiment to see which work. --

[issue24563] [doc] Encoding declaration: doc supported encodings

Change by Irit Katriel : -- keywords: +easy title: Encoding declaration: doc supported encodings -> [doc] Encoding declaration: doc supported encodings versions: +Python 3.10, Python 3.11, Python 3.9 -Python 2.7, Python 3.4, Python 3.5, Python

[issue47000] Make encoding="locale" uses locale encoding even in UTF-8 mode is enabled.

case now, but I'm also > not against it. Victor didn't mention about "no underscore" convention. I just want to see preference from others. I will remove the underscore. > I would like to reiterate my concern with the "locale" encoding, though. > > As mentioned earlier

[issue47000] Make encoding="locale" uses locale encoding even in UTF-8 mode is enabled.

would like to reiterate my concern with the "locale" encoding, though. As mentioned earlier, I believe it adds too much magic. It would be better to leave this in the hands of the applications and not try to guess the correct encoding. It's better to expose easy to use APIs to access t

[issue47000] Make encoding="locale" uses locale encoding even in UTF-8 mode is enabled.

Inada Naoki added the comment: @vstiner Since UTF-8 mode affects `locale.getpreferredencoding(False)`, I need to decide alternative API in the PEP 686. If no objections, I will choose `locale.get_encoding()` for current locale encoding (ACP on Windows). See https://github.com/python/peps

[issue47000] Make encoding="locale" uses locale encoding even in UTF-8 mode is enabled.

Inada Naoki added the comment: I am not sure about we really need "locale encoding at Python startup". For this issue, I don't want to change `encoding="locale"` behavior except ignore UTF-8 mode. So what I want is "current locale encoding" or ANSI codepage

[issue47000] Make encoding="locale" uses locale encoding even in UTF-8 mode is enabled.

STINNER Victor added the comment: sys.getlocaleencoding() versus locale.getencoding(). For me, the Python locale module should use the C API to access the Unix locales like LC_CTYPE, nl_langinfo(CODESET), etc. The sys module are more for things specific to Python, like

[issue47000] Make encoding="locale" uses locale encoding even in UTF-8 mode is enabled.

Change by Inada Naoki : -- pull_requests: +30157 pull_request: https://github.com/python/cpython/pull/32068 ___ Python tracker ___

[issue47000] Make encoding="locale" uses locale encoding even in UTF-8 mode is enabled.

Inada Naoki added the comment: > * sys.getfilesystemencoding(): Python filesystem encoding, return "UTF-8" if > the Python UTF-8 Mode is enabled Yes, althoguh PYTHONLEGACYWINDOWSFSENCODING takes priority. > * locale.getencoding(): Get the locale encoding, LC_CT

[issue47000] Make encoding="locale" uses locale encoding even in UTF-8 mode is enabled.

STINNER Victor added the comment: I propose: * sys.getfilesystemencoding(): Python filesystem encoding, return "UTF-8" if the Python UTF-8 Mode is enabled * Implementation: PyConfig.filesystem_encoding * https://docs.python.org/dev/library/sys.html#sys.getfilesystemencoding

[issue47000] Make encoding="locale" uses locale encoding even in UTF-8 mode is enabled.

STINNER Victor added the comment: > But some user want to use UTF-8 mode to change default encoding in their > Python environments without waiting Python default encoding changed. IMO it's a different use case and it should be a different thing. Changing encoding="locale" t

[issue47000] Make encoding="locale" uses locale encoding even in UTF-8 mode is enabled.

STINNER Victor added the comment: > Is it safe to use `locale.getlocale(locale.LC_CTYPE)[1] or "UTF-8"`? I would like to deprecate getlocale(), see bpo-43557. -- ___ Python tracker

[issue47000] Make encoding="locale" uses locale encoding even in UTF-8 mode is enabled.

Change by Inada Naoki : -- keywords: +patch pull_requests: +30091 stage: -> patch review pull_request: https://github.com/python/cpython/pull/32003 ___ Python tracker ___

[issue47000] Make encoding="locale" uses locale encoding even in UTF-8 mode is enabled.

Marc-Andre Lemburg added the comment: FWIW: I don't think the "locale" encoding is a good idea. Instead of trying to fix this to make it more usable, I'd suggest to deprecate and remove it again. When it comes to encodings, explicit is better than implicit. If an application wan

[issue47000] Make encoding="locale" uses locale encoding even in UTF-8 mode is enabled.

Inada Naoki added the comment: I created another topic relating this issue. https://discuss.python.org/t/add-legacy-text-encoding-option-to-make-utf-8-default/14281 If we add another option (e.g. legacy_text_encoding), we do not need to change UTF-8 mode behavior

[issue47000] Make encoding="locale" uses locale encoding even in UTF-8 mode is enabled.

STINNER Victor added the comment: There are multiple "locale encodings": * "current" locale encoding: locale.nl_langinfo(locale.CODESET) * "Python" locale encoding: locale.getpreferredencoding(False), ignore the locale in UTF-8 Mode (always return "UT

[issue47000] Make encoding="locale" uses locale encoding even in UTF-8 mode is enabled.

STINNER Victor added the comment: > So I think `encoding="locale"` should use real locale encoding (ACP on > Windows) regardless UTF-8 mode is enabled or not. If you want to change the default, would it be possible to add a function to g

[issue47000] Make encoding="locale" uses locale encoding even in UTF-8 mode is enabled.

Inada Naoki added the comment: I created a related topic on discuss.python.org. https://discuss.python.org/t/jep-400-utf-8-by-default-and-future-of-python/14246 If we recommend `PYTHONUTF8` as opt-in "UTF-8 by default", `encoding="locale"` should locale encoding in UTF-

[issue47000] Make encoding="locale" uses locale encoding even in UTF-8 mode is enabled.

New submission from Inada Naoki : Currently, `encoding="locale"` is just shortcut of `encoding=locale.getpreferredencoding(False)`. `encoding="locale"` means that "locale encoding should be used here, even if Python default encoding is changed to UTF-8".

[issue46598] ElementTree: wrong XML prolog for the utf-8-sig encoding

Change by Ned Deily : -- nosy: +eli.bendersky, scoder versions: +Python 3.11 ___ Python tracker ___ ___ Python-bugs-list mailing

[issue46598] ElementTree: wrong XML prolog for the utf-8-sig encoding

New submission from Petr Prikryl : When ElementTree object is to be written to the file, and when BOM is needed, the 'utf-8-sig' can be used for the purpose. However, the XML prolog then looks like... ... and that encoding in the prolog makes no sense. Therefore, the utf-8-sig

[issue25948] Invalid MIME encoding generated by email.mime (line too long)

Change by jiahua wang : -- keywords: +patch nosy: +wangjiahua nosy_count: 3.0 -> 4.0 pull_requests: +29159 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30980 ___ Python tracker

[issue11322] encoding package's normalize_encoding() function is too slow

Change by Gregory P. Smith : -- nosy: +gregory.p.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue31116] base85 z85 variant encoding

Change by Matan Perelman : -- keywords: +patch nosy: +matan1008 nosy_count: 3.0 -> 4.0 pull_requests: +28796 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30598 ___ Python tracker

[issue46143] [docs] IO > Text Encoding info outdated

mode is never enabled automatically in Windows. In contrast to POSIX, the locale encoding in Windows is unrelated to the current LC_CTYPE locale. Instead, the locale encoding gets set to the process code page, which is based on the system locale by default and never changes while a process

[issue46143] [docs] IO > Text Encoding info outdated

Inada Naoki added the comment: UTF-8 mode is not enabled by default. So locale encoding is still the default encoding. -- nosy: +methane ___ Python tracker <https://bugs.python.org/issue46

[issue46143] [docs] IO > Text Encoding info outdated

New submission from David Gilbertson : On this page: https://docs.python.org/3/library/io.html#text-encoding it says "there is no concrete plan as of yet, Python may change the default text file encoding to UTF-8 in the future". On this page https://docs.python.org/3/library/os

[issue25948] Invalid MIME encoding generated by email.mime (line too long)

Change by Irit Katriel : -- versions: +Python 3.10, Python 3.11, Python 3.9 -Python 3.5 ___ Python tracker ___ ___ Python-bugs-list

[issue39757] EmailMessage bad encoding for international domain

Irit Katriel added the comment: Reproduced on 3.11. -- nosy: +iritkatriel versions: +Python 3.10, Python 3.11, Python 3.9 -Python 3.5 ___ Python tracker ___

[issue1525919] email package content-transfer-encoding behaviour changed

Change by Irit Katriel : -- versions: +Python 3.10, Python 3.11, Python 3.9 -Python 2.7, Python 3.2, Python 3.3, Python 3.4 ___ Python tracker ___

[issue1525919] email package content-transfer-encoding behaviour changed

e.text >>> mt = email.mime.text.MIMEText('Ta mère', 'plain', 'utf-8') >>> print(mt.as_string()) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 VGEgbcOocmU= >>> email.encoders.encode_quopri(mt) >>> pri

[issue1525919] email package content-transfer-encoding behaviour changed

Irit Katriel added the comment: The encoding functions are now doing orig = msg.get_payload(decode=True) Does this fix the double-encoding issue? This change was made in https://github.com/python/cpython/commit/00ae435deef434f471e39bea3f3ab3a3e3cd90fe -- nosy: +iritkatriel status

[issue4733] Add a "decode to declared encoding" version of urlopen to urllib

Daniel Diniz added the comment: As Victor notes, this is a controversial issue. And I'll add that the need for this feature seems not to have been brought up up in over a decade. So I'm closing this. -- resolution: -> rejected stage: patch review -> resolved status: open -> closed

[issue16223] [doc] untokenize returns a string if no encoding token is recognized

Irit Katriel added the comment: The doc has been updated by now: "It returns bytes, encoded using the ENCODING token, which is the first token sequence output by tokenize(). If there is no encoding token in the input, it returns a str instead." https://docs.python.org

[issue19941] python -m imports non-ASCII .py file without encoding declaration

STINNER Victor added the comment: I confirm: Python 3.10 works as expected. Python 3.10 fails with the same SyntaxError using "python script.py" or "python -m script" if the script contains non-ASCII characters but is not encoded to UTF-8. vstinner@apu$ python3 test.py File

[issue19941] python -m imports non-ASCII .py file without encoding declaration

Eryk Sun added the comment: test.py is a UTF-8 file, which is the default source encoding in Python 3. It fails as expected if the test script is encoded differently, such as Latin-1, unless the source encoding is declared. -- nosy: +eryksun resolution: -> out of date st

[issue19941] python -m imports non-ASCII .py file without encoding declaration

Change by Irit Katriel : -- components: +Interpreter Core ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue19941] python -m imports non-ASCII .py file without encoding declaration

Irit Katriel added the comment: On 3.11 both are working (on a Mac): cpython-1 % python -m tt ¡Hello world! cpython-1 % ./python.exe -c 'import tt' ¡Hello world! -- nosy: +iritkatriel ___ Python tracker

[issue17305] IDNA2008 encoding is missing

Change by Eric Case : -- nosy: +case ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36841] Supporting customization of float encoding in JSON

Change by Mark Dickinson : -- nosy: +mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36841] Supporting customization of float encoding in JSON

Min RK added the comment: We just ran into this in Jupyter where we've removed a pre-processing step for data structures passed to json.dumps, which took care of this, but was expensive https://github.com/jupyter/jupyter_client/pull/706 My expectation was that our `default` would be called

[issue36841] Supporting customization of float encoding in JSON

Change by Min RK : -- nosy: +minrk nosy_count: 5.0 -> 6.0 pull_requests: +27016 pull_request: https://github.com/python/cpython/pull/28648 ___ Python tracker ___

[issue36819] Crash during encoding using UTF-16/32 and custom error handler

Walter Dörwald added the comment: The original specification (PEP 293) required that an error handler called for encoding *must* return a replacement string (not bytes). This returned string must then be encoded again. Only if this fails an exception must be raised. Returning bytes from

[issue36819] Crash during encoding using UTF-16/32 and custom error handler

Marc-Andre Lemburg added the comment: On 29.09.2021 10:41, Serhiy Storchaka wrote: > > Restricting the returned position to be strictly larger than start would > solve the problem with infinite loop and OOM. But this is a different issue. Yes, this would make sense, since having the codec

[issue36819] Crash during encoding using UTF-16/32 and custom error handler

Serhiy Storchaka added the comment: Restricting the returned position to be strictly larger than start would solve the problem with infinite loop and OOM. But this is a different issue. -- ___ Python tracker

[issue36819] Crash during encoding using UTF-16/32 and custom error handler

Change by Marc-Andre Lemburg : -- nosy: +doerwalter ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36819] Crash during encoding using UTF-16/32 and custom error handler

Change by Marc-Andre Lemburg : -- components: +Unicode nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue36819] Crash during encoding using UTF-16/32 and custom error handler

son for this: the codec may not be able to correctly determine the end of the sequence and so the end value presented by the codec is not necessarily a valid start to continue encoding/decoding. The error handler can e.g. choose to skip more input characters by trying to find the next valid sequence. In the exam

[issue36819] Crash during encoding using UTF-16/32 and custom error handler

STINNER Victor added the comment: > We could just forbid error handlers returning position not in the range > (start , end] Yeah, that sounds like a reasonable solution. I don't see the point of returning a position outside this range. What would be the use case? For me, the only corner

[issue36819] Crash during encoding using UTF-16/32 and custom error handler

Change by Serhiy Storchaka : -- pull_requests: +26973 pull_request: https://github.com/python/cpython/pull/28593 ___ Python tracker ___

[issue36819] Crash during encoding using UTF-16/32 and custom error handler

Serhiy Storchaka added the comment: I am working on it, since it is more complex issue, and PR 13134 does not solve it. 1. This bug affects also other codecs implemented in C: ASCII, Latin1, UTF-8, etc. 2. It still crashes in UTF-16/32 encoders if the error handler returns a position less

[issue41137] pdb uses the locale encoding for .pdbrc

STINNER Victor added the comment: New changeset ec7ffa4b5b262369f726a54e145e9c03eaeb4c1a by Victor Stinner in branch 'main': bpo-41137: Reorganize What's New in Python 3.11 (GH-28518) https://github.com/python/cpython/commit/ec7ffa4b5b262369f726a54e145e9c03eaeb4c1a --

[issue41137] pdb uses the locale encoding for .pdbrc

Change by STINNER Victor : -- nosy: +vstinner nosy_count: 4.0 -> 5.0 pull_requests: +26909 pull_request: https://github.com/python/cpython/pull/28518 ___ Python tracker ___

[issue36819] Crash during encoding using UTF-16/32 and custom error handler

Irit Katriel added the comment: Reproduced on 3.11. -- nosy: +iritkatriel versions: +Python 3.10, Python 3.11, Python 3.9 -Python 3.7, Python 3.8 ___ Python tracker ___

[issue44836] shutil _unpack_zipfile filename encoding issue

New submission from Yogendra kumar soni : shutil _unpack_zipfile uses takes filename using name = info.filename if files are created in a machine that uses different encoding say utf-8 containing u'\u201c' in filename and the machine where we are extracting has a different encoding say Latin

[issue37715] 2to3 set default encoding

Change by Benjamin Peterson : -- resolution: -> wont fix stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue37715] 2to3 set default encoding

Thomas Grainger added the comment: lib2to3 is deprecated and is pending removal, so I think this can be closed -- nosy: +graingert ___ Python tracker ___

[issue41137] pdb uses the locale encoding for .pdbrc

Change by Inada Naoki : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.11 ___ Python tracker ___

[issue41137] pdb uses the locale encoding for .pdbrc

Inada Naoki added the comment: New changeset 58248d94379b202ccce3e45b1d1830ca47683273 by Srinivas Reddy Thatiparthy (శ్రీనివాస్ రెడ్డి తాటిపర్తి) in branch 'main': bpo-41137: Use utf-8 encoding while reading .pdbrc files (GH-21263) https://github.com/python/cpython/commit

[issue24339] iso6937 encoding missing

Maarten Derickx added the comment: Hi Marc-Andre Lemburg, Thanks for your responses and guidance. At least your pointers to charmap_encode and charmap_decode helped, since it shows at least what the general idea is on how to deal with these types of encodings. In the mean time I did

[issue24339] iso6937 encoding missing

Marc-Andre Lemburg added the comment: Right, the charmap codec was built with the Unicode Consortium mappings in mind. However, you may have some luck decoding the two byte chars in ISO 6937 using combining code points in Unicode. With some extra post processing you could also normalize the

[issue24339] iso6937 encoding missing

where a single encoded byte corresponds to multiple unicode points. However iso6937 is a mixed length encoding, meaning in this specific case that unicode characters sometimes need to be encoded as a single byte and sometimes with two bytes. For example chr(0x00c0) should be encoded as b'\xc1

[issue17305] IDNA2008 encoding is missing

Andrei Kulakov added the comment: Maybe deprecate idna so that users are strongly prompted to consider the pypi idna? -- nosy: +andrei.avk ___ Python tracker ___

[issue24339] iso6937 encoding missing

Maarten Derickx added the comment: Hi Marc-Andre Lemburg, Thanks for your reply. I tried using gencodec.py as could be downloaded from https://github.com/python/cpython/blob/main/Tools/unicode/gencodec.py as you mentioned. However the code in gencodec.py seems to be in a much worse shape

[issue24339] iso6937 encoding missing

Marc-Andre Lemburg added the comment: Maarten, the code posted on bugs is copyrighted by the person who wrote it. We can only accept it for inclusion in Python after the CLA has been signed, since then we are allowed to relicense it. As a result you can only take John's code and post it

[issue24339] iso6937 encoding missing

Maarten Derickx added the comment: Is there any way to contact John Helour? I would still very much like to put this package on github and pypi. And would like to ask him permission for licensing. Or is there some standard open source license under which all code uploaded to

[issue43667] Solaris: Fix broken Unicode encoding in non-UTF locales

Pablo Galindo Salgado added the comment: New changeset f87d2038fadd9c067d50fb2f1d7c2f37b9f3893a by Miss Islington (bot) in branch '3.10': bpo-43667: Add news fragment for Solaris changes (GH-26405) (GH-26498) https://github.com/python/cpython/commit/f87d2038fadd9c067d50fb2f1d7c2f37b9f3893a

[issue29479] httplib: could not skip "ACCEPT-ENCODING" header

Irit Katriel added the comment: As Martin has stated, this can be achieved with putrequest as explained in the doc: https://docs.python.org/3.10/library/http.client.html#http.client.HTTPConnection.putrequest -- nosy: +iritkatriel resolution: -> not a bug stage: test needed ->

[issue18961] Non-UTF8 encoding line

Irit Katriel added the comment: I've reproduced the same in 3.11: > .\python.bat nonutf8_coding_line.py Running Release|x64 interpreter... > .\python.bat -m tokenize nonutf8_coding_line.py Running Release|x64 interpreter... nonutf8_coding_line.py: error: invalid or missing en

[issue43667] Solaris: Fix broken Unicode encoding in non-UTF locales

Change by miss-islington : -- pull_requests: +25094 pull_request: https://github.com/python/cpython/pull/26498 ___ Python tracker ___

[issue43667] Solaris: Fix broken Unicode encoding in non-UTF locales

STINNER Victor added the comment: I merged your PR and backported it to add a NEWS entry, thanks. -- ___ Python tracker ___ ___

[issue43667] Solaris: Fix broken Unicode encoding in non-UTF locales

STINNER Victor added the comment: New changeset 427232f9d221d54870fa3e89bd1dac55cf42243f by Miss Islington (bot) in branch '3.9': bpo-43667: Add news fragment for Solaris changes (GH-26405) (GH-26410) https://github.com/python/cpython/commit/427232f9d221d54870fa3e89bd1dac55cf42243f

[issue43667] Solaris: Fix broken Unicode encoding in non-UTF locales

STINNER Victor added the comment: New changeset 0574b0686d76e6f9199f800b5f32bd56eaff3c77 by Miss Islington (bot) in branch '3.10': bpo-43667: Add news fragment for Solaris changes (GH-26405) (GH-26409) https://github.com/python/cpython/commit/0574b0686d76e6f9199f800b5f32bd56eaff3c77

[issue43667] Solaris: Fix broken Unicode encoding in non-UTF locales

Change by miss-islington : -- nosy: +miss-islington nosy_count: 3.0 -> 4.0 pull_requests: +25003 pull_request: https://github.com/python/cpython/pull/26409 ___ Python tracker

[issue43667] Solaris: Fix broken Unicode encoding in non-UTF locales

Change by miss-islington : -- pull_requests: +25004 pull_request: https://github.com/python/cpython/pull/26410 ___ Python tracker ___

[issue43667] Solaris: Fix broken Unicode encoding in non-UTF locales

STINNER Victor added the comment: New changeset 164a4f46d1606e21d82babc010e397a9116e6730 by Jakub Kulík in branch 'main': bpo-43667: Add news fragment for Solaris changes (GH-26405) https://github.com/python/cpython/commit/164a4f46d1606e21d82babc010e397a9116e6730 --

[issue43667] Solaris: Fix broken Unicode encoding in non-UTF locales

Change by Jakub Kulik : -- pull_requests: +24998 pull_request: https://github.com/python/cpython/pull/26405 ___ Python tracker ___

[issue43667] Solaris: Fix broken Unicode encoding in non-UTF locales

STINNER Victor added the comment: I close the issue, but you can still reference the bpo issue number for your PR with the changelog (NEWS) entry. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue43667] Solaris: Fix broken Unicode encoding in non-UTF locales

Jakub Kulik added the comment: Sorry for delayed response. Considering that we are not delivering or using 3.8 in any way and this issue doesn't seem to impact anybody else, we can omit the backport to 3.8. I will prepare another PR with a news fragment, and after that, this can be

[issue43667] Solaris: Fix broken Unicode encoding in non-UTF locales

STINNER Victor added the comment: Do you want to attempt to backport the fix to 3.8, or can this issue be closed? -- ___ Python tracker ___

[issue43667] Solaris: Fix broken Unicode encoding in non-UTF locales

STINNER Victor added the comment: Backport to 3.8 may be more complicated. It's up to you to decide if you want to backport it or not. I merged your 3.9 backport, it looks very close to the change made in the main branch. -- ___ Python tracker

[issue43667] Solaris: Fix broken Unicode encoding in non-UTF locales

STINNER Victor added the comment: New changeset d3cc68900dc99966007112f884779895daefc7db by Jakub Kulík in branch '3.9': [3.9] bpo-43667: Fix broken Unicode encoding in non-UTF locales on Solaris (GH-25096) (GH-25847) https://github.com/python/cpython/commit

  1   2   3   4   5   6   7   8   9   10   >