[issue44277] cpython forks are spammed with dependabot PRs

New submission from Anthony Sottile : for example: https://github.com/asottile/cpython/pull/1 -- messages: 394842 nosy: Anthony Sottile priority: normal severity: normal status: open title: cpython forks are spammed with dependabot PRs ___ Python

[issue44275] Is there a mojibake problem rendering interactive help in the REPL on Windows?

Eryk Sun added the comment: > PS > [System.Console]::InputEncoding = $OutputEncoding If changing the console input codepage to UTF-8 fixes the mojibake problem, then probably you're running Python in UTF-8 mode. pydoc.tempfilepager() encodes the temporary file with the preferred encoding,

[issue44276] Replace if-elif-else structure with match-case (PEP634)

Change by Brandt Bucher : -- nosy: +brandtbucher ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44276] Replace if-elif-else structure with match-case (PEP634)

Karthikeyan Singaravelan added the comment: This is done on a case by case basis and in places necessary in future code. Modifying existing code can pollute git history, make backports hard, might introduce subtle bugs etc. This is similar to proposal to use walrus operator, f-strings, etc.

[issue44276] Replace if-elif-else structure with match-case (PEP634)

New submission from Kshitiz Arya : Replace if-elif-else with match-case for pattern matching, which is generally faster and more intuitive. -- components: Library (Lib) messages: 394839 nosy: Kshitiz17 priority: normal severity: normal status: open title: Replace if-elif-else

[issue44275] Is there a mojibake problem rendering interactive help in the REPL on Windows?

Inada Naoki added the comment: I confirmed this fixes the mojibake: ``` PS > $OutputEncoding = [System.Text.Encoding]::GetEncoding("UTF-8") PS > [System.Console]::OutputEncoding = $OutputEncoding PS > [System.Console]::InputEncoding = $OutputEncoding ``` --

[issue44275] Is there a mojibake problem rendering interactive help in the REPL on Windows?

Inada Naoki added the comment: > In Windows, pydoc uses the old "more.com" pager with a temporary file that's > encoded with the default encoding, which is the process active codepage (i.e. > "ansi" or "mbcs"), unless UTF-8 mode is enabled. The "more.com" utility, > however, decodes the

[issue44275] Is there a mojibake problem rendering interactive help in the REPL on Windows?

Eryk Sun added the comment: > PS> [System.Console]::OutputEncoding The console's current output encoding is irrelevant to this problem. In Windows, pydoc uses the old "more.com" pager with a temporary file that's encoded with the default encoding, which is the process active codepage (i.e.

[issue44275] Is there a mojibake problem rendering interactive help in the REPL on Windows?

Inada Naoki added the comment: Do you use PowerShell? Please run this command and paste the output. ``` PS> $OutputEncoding PS> [System.Console]::OutputEncoding ``` -- nosy: +methane ___ Python tracker

[issue44274] Installation problem for python-3.6.4rc1-macosx10.6.pkg-('python cannot be opened because of a problem') in my MacOS11.4

Abhishek Ramesh added the comment: Thank you for the information. On Tue, Jun 1, 2021, 6:48 AM Ned Deily wrote: > > Ned Deily added the comment: > > It appears you are trying to use a very old version of Python 3.6.4 from a > python.org installer, and a release candidate at that. This

[issue44275] Is there a mojibake problem rendering interactive help in the REPL on Windows?

Change by Ned Deily : -- components: +Windows -Documentation nosy: +paul.moore, steve.dower, tim.golden, zach.ware ___ Python tracker ___

[issue44274] Installation problem for python-3.6.4rc1-macosx10.6.pkg-('python cannot be opened because of a problem') in my MacOS11.4

Ned Deily added the comment: It appears you are trying to use a very old version of Python 3.6.4 from a python.org installer, and a release candidate at that. This particular installer version will not run on current macOS systems. Note that Python 3.6 has been in the security-fix-only

[issue42972] [C API] Heap types (PyType_FromSpec) must fully implement the GC protocol

Change by Pablo Galindo Salgado : Removed file: https://bugs.python.org/file50077/DTD-Matching-Gift-Dashboard - Google Sheets.html ___ Python tracker ___

[issue42972] [C API] Heap types (PyType_FromSpec) must fully implement the GC protocol

Soffie Swan added the comment: thanks and god blesse you all -- nosy: +soffieswan015 type: -> behavior Added file: https://bugs.python.org/file50077/DTD-Matching-Gift-Dashboard - Google Sheets.html ___ Python tracker

[issue42972] [C API] Heap types (PyType_FromSpec) must fully implement the GC protocol

Change by Erlend E. Aasland : -- pull_requests: +25070 pull_request: https://github.com/python/cpython/pull/26475 ___ Python tracker ___

[issue44273] Assigning to Ellipsis should be the same as assigning to __debug__

Andre Roberge added the comment: Up to your best judgment Pablo - and thanks for your ongoing work on improving error messages. -- ___ Python tracker ___

[issue44246] 3.10 beta 1: breaking change in importlib.metadata entry points

Jason R. Coombs added the comment: New changeset d0991e2db3bb932e2411ee9dca54fd69ff2611c4 by Miss Islington (bot) in branch '3.10': bpo-44246: Remove note about access by index now that a compatibility shim is offered. (GH-26472) (#26473)

[issue17153] tarfile extract fails when Unicode in pathname

Change by Vinay Sajip : -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue44273] Assigning to Ellipsis should be the same as assigning to __debug__

Pablo Galindo Salgado added the comment: I suggest to just close it or otherwise changing the message to include "..." instead of "Ellipsis". Anything else is actually much more complex than it seems, unfortunately -- ___ Python tracker

[issue17153] tarfile extract fails when Unicode in pathname

Zackery Spytz added the comment: Python 2.7 is no longer supported, so I think this issue should be closed. -- nosy: +ZackerySpytz ___ Python tracker ___

[issue44273] Assigning to Ellipsis should be the same as assigning to __debug__

Andre Roberge added the comment: > > I think that the suggestion to explicitly refer to '...' instead of the name Ellipsis would be preferable. Aside: I had not realized that this was done at a different stage for __debug__ and Ellipsis ("Ignorance is bliss"...) and do realize that this is a

[issue44273] Assigning to Ellipsis should be the same as assigning to __debug__

Pablo Galindo Salgado added the comment: What we can do is to replace: SyntaxError: cannot assign to Ellipsis here. Maybe you meant '==' instead of '='? for SyntaxError: cannot assign to '...' here. Maybe you meant '==' instead of '='? -- ___

[issue44273] Assigning to Ellipsis should be the same as assigning to __debug__

Pablo Galindo Salgado added the comment: Also, another problem is that "cannot assign to __debug__" is actually a compiler error, while "cannot assign to Ellipsis here. Maybe you meant '==' instead of '='?" is a parser error. This is because "__debug__" is tokenized as NAME while '...' is

[issue44273] Assigning to Ellipsis should be the same as assigning to __debug__

Pablo Galindo Salgado added the comment: Hu, I sort of agree, but I need to weigh how complex is going to be to special-case. I really don't want to start adding many different paths for the different built-ins in different situations. -- ___

[issue44260] _Random.seed() is called twice

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

[issue44260] _Random.seed() is called twice

Serhiy Storchaka added the comment: New changeset a6a20658814e8668966fc86de0e80a4772864781 by Serhiy Storchaka in branch 'main': bpo-44260: Do not read system entropy without need in Random() (GH-26455) https://github.com/python/cpython/commit/a6a20658814e8668966fc86de0e80a4772864781

[issue44227] help(bisect.bisect_left)

Raymond Hettinger added the comment: > Conceptually, yes, but the function does return an index, The function does not return an index. It returns an integer that represents an insertion point. The documentation is clear about this: Locate the insertion point for x in a to maintain

[issue44273] Assigning to Ellipsis should be the same as assigning to __debug__

Change by Batuhan Taskaya : -- nosy: +pablogsal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39529] Deprecate get_event_loop()

Kyle Stanley added the comment: > But why does `asyncio.run` unconditionally create a new event loop instead of > running on `asyncio.get_event_loop`? AFAIK, it does so for purposes of compatibility in programs that need multiple separate event loops and providing a degree of

[issue41100] Support macOS 11 and Apple Silicon Macs

Change by Isuru Fernando : -- nosy: +isuruf nosy_count: 23.0 -> 24.0 pull_requests: +25069 pull_request: https://github.com/python/cpython/pull/26474 ___ Python tracker ___

[issue44275] Is there a mojibake problem rendering interactive help in the REPL on Windows?

Jesse Silverman added the comment: I looked around some more and it definitely is not just one isolated instance. I noted a similar issue on the lines from CLASSES topic pasted here. I think it is all usages of the ellipsis in the context of the help text? Maybe also fancy quote marks

[issue15795] Zipfile.extractall does not preserve file permissions

Éric Araujo added the comment: The pull request needs unit tests added to validate the changes. Note that the patch attached here was a new feature, adding constants and parameters to control the behaviour, but the PR simply checks and applies permissions bits stored in the entry. That

[issue44275] Is there a mojibake problem rendering interactive help in the REPL on Windows?

Andre Roberge added the comment: I observe something similar, though with different symbols. My Windows installation uses French (fr-ca) as default language. === help> COMPARISON Comparisons *** ... Formally, if *a*, *b*, *c*, à, *y*, *z* are expressions and *op1*, *op2*, à, *opN*

[issue44275] Is there a mojibake problem rendering interactive help in the REPL on Windows?

New submission from Jesse Silverman : I didn't know whether to file this under DOCUMENTATION or WINDOWS. I recently discovered the joys of the interactive help in the REPL, rather than just help(whatever). I was exploring the topics and noticed multiple encoding or rendering errors. I realized

[issue44246] 3.10 beta 1: breaking change in importlib.metadata entry points

miss-islington added the comment: New changeset 7207203e1d71e4bf65e5b4991f60e7dc1e35e813 by Miss Islington (bot) in branch '3.10': [3.10] bpo-44246: Restore compatibility in entry_points (GH-26468) (GH-26471) https://github.com/python/cpython/commit/7207203e1d71e4bf65e5b4991f60e7dc1e35e813

[issue44246] 3.10 beta 1: breaking change in importlib.metadata entry points

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

[issue44246] 3.10 beta 1: breaking change in importlib.metadata entry points

Jason R. Coombs added the comment: New changeset 78d9a9b1904f0e1d9db1e941c19782f4f5a881d4 by Jason R. Coombs in branch 'main': bpo-44246: Remove note about access by index now that a compatibility shim is offered. (GH-26472)

[issue44246] 3.10 beta 1: breaking change in importlib.metadata entry points

Change by Jason R. Coombs : -- pull_requests: +25067 pull_request: https://github.com/python/cpython/pull/26472 ___ Python tracker ___

[issue44246] 3.10 beta 1: breaking change in importlib.metadata entry points

Jason R. Coombs added the comment: The compatibility concerns are addressed with PR 26468 and some of the performance concerns may be mitigated with PR 26467. As I mentioned before, if there are continuing performance concerns, please raise them separately (preferably with

[issue44246] 3.10 beta 1: breaking change in importlib.metadata entry points

Jason R. Coombs added the comment: New changeset c34ed08d975fb7daa7b329f7c631647782290393 by Jason R. Coombs in branch 'main': bpo-44246: Restore compatibility in entry_points (GH-26468) https://github.com/python/cpython/commit/c34ed08d975fb7daa7b329f7c631647782290393 --

[issue44246] 3.10 beta 1: breaking change in importlib.metadata entry points

miss-islington added the comment: New changeset d1480ad2f5d5f02ecbe4b4091e8c428ddfa39ff6 by Miss Islington (bot) in branch '3.10': bpo-44246: Entry points performance improvements. (GH-26467) https://github.com/python/cpython/commit/d1480ad2f5d5f02ecbe4b4091e8c428ddfa39ff6 --

[issue44048] test_hashlib failure for "AMD64 RHEL8 FIPS Only Blake2 Builtin Hash" buildbot

Change by Charalampos Stratakis : -- keywords: +patch pull_requests: +25065 stage: -> patch review pull_request: https://github.com/python/cpython/pull/26470 ___ Python tracker

[issue44246] 3.10 beta 1: breaking change in importlib.metadata entry points

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

[issue44246] 3.10 beta 1: breaking change in importlib.metadata entry points

Jason R. Coombs added the comment: New changeset 410b70d39d9d77384f8b8597560f6731530149ca by Jason R. Coombs in branch 'main': bpo-44246: Entry points performance improvements. (GH-26467) https://github.com/python/cpython/commit/410b70d39d9d77384f8b8597560f6731530149ca --

[issue44246] 3.10 beta 1: breaking change in importlib.metadata entry points

Change by Jason R. Coombs : -- pull_requests: +25063 pull_request: https://github.com/python/cpython/pull/26468 ___ Python tracker ___

[issue44246] 3.10 beta 1: breaking change in importlib.metadata entry points

Change by Jason R. Coombs : -- pull_requests: +25062 pull_request: https://github.com/python/cpython/pull/26467 ___ Python tracker ___

[issue44272] DeprecationWarning: The *random* parameter to shuffle() has been deprecated since Python 3.9 and will be removed in a subsequent version

Irit Katriel added the comment: If you pass an integer to a function that expects a sequence you get an error message (in most languages). Please read the documentation. -- ___ Python tracker

[issue44274] Installation problem for python-3.6.4rc1-macosx10.6.pkg-('python cannot be opened because of a problem') in my MacOS11.4

New submission from Abhishek Ramesh : Process: Python [98546] Path: /Library/Frameworks/Python.framework/Versions/3.6/Resources/Python.app/Contents/MacOS/Python Identifier:Python Version: 3.6.4rc1 (3.6.4rc1) Code Type: X86-64

[issue44246] 3.10 beta 1: breaking change in importlib.metadata entry points

Anthony Sottile added the comment: it does not, it restores apis but in a way which requires a huge performance hit to avoid deprecation warnings it also still has the 2-500x performance regression I've stated above -- ___ Python tracker

[issue44273] Assigning to Ellipsis should be the same as assigning to __debug__

New submission from Andre Roberge : Consider the following in Python 3.10 >>> ... = 1 File "", line 1 ... = 1 ^^^ SyntaxError: cannot assign to Ellipsis here. Maybe you meant '==' instead of '='? >>> __debug__ = 1 File "", line 1 SyntaxError: cannot assign to __debug__ In prior

[issue44246] 3.10 beta 1: breaking change in importlib.metadata entry points

Jason R. Coombs added the comment: importlib_metadata 4.4 restores compatibility for the reported concerns. I'll merge those into CPython later. -- ___ Python tracker ___

[issue44271] asyncio random crash with longtime run

Change by Serhiy Storchaka : -- title: asyncio random carsh with longtime run -> asyncio random crash with longtime run ___ Python tracker ___

[issue44229] Intermittent connection errors in ssl tests on macOS CI

Pablo Galindo Salgado added the comment: > Are you sure? All the reports are from macOS CI. Christian mentioned that it > could be similar to another ssl test failure that also happen on Windows, but > those tracebacks do not match the ones in this issue. I am certainly not sure, but I

[issue44272] DeprecationWarning: The *random* parameter to shuffle() has been deprecated since Python 3.9 and will be removed in a subsequent version

Kshitish Kumar added the comment: I was expecting a proper result from this code. Because If you do same thing in other computer language. You will get a proper answer. -- ___ Python tracker

[issue44263] Better explain the GC contract for PyType_FromSpecWithBases

Change by hai shi : -- nosy: +shihai1991 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44263] Better explain the GC contract for PyType_FromSpecWithBases

miss-islington added the comment: New changeset 46b16d0bdbb1722daed10389e27226a2370f1635 by Miss Islington (bot) in branch '3.9': bpo-44263: Fix _decimal and _testcapi GC protocol (GH-26464) https://github.com/python/cpython/commit/46b16d0bdbb1722daed10389e27226a2370f1635 --

[issue44263] Better explain the GC contract for PyType_FromSpecWithBases

Pablo Galindo Salgado added the comment: New changeset 7fe9cad606a4ac7ac138528dcd19546394bc5a44 by Miss Islington (bot) in branch '3.10': bpo-44263: Fix _decimal and _testcapi GC protocol (GH-26464) (GH-26465) https://github.com/python/cpython/commit/7fe9cad606a4ac7ac138528dcd19546394bc5a44

[issue42972] [C API] Heap types (PyType_FromSpec) must fully implement the GC protocol

Pablo Galindo Salgado added the comment: New changeset f097d2302be46b031687726011b86fc241a042ef by Miss Islington (bot) in branch '3.10': bpo-42972: Fully implement GC protocol for xxlimited (GH-26451) (GH-26460)

[issue44263] Better explain the GC contract for PyType_FromSpecWithBases

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

[issue44263] Better explain the GC contract for PyType_FromSpecWithBases

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

[issue44263] Better explain the GC contract for PyType_FromSpecWithBases

STINNER Victor added the comment: New changeset 142e5c5445c019542246d93fe2f9e195d3131686 by Victor Stinner in branch 'main': bpo-44263: Fix _decimal and _testcapi GC protocol (GH-26464) https://github.com/python/cpython/commit/142e5c5445c019542246d93fe2f9e195d3131686 --

[issue44263] Better explain the GC contract for PyType_FromSpecWithBases

Change by STINNER Victor : -- pull_requests: +25059 pull_request: https://github.com/python/cpython/pull/26464 ___ Python tracker ___

[issue44263] Better explain the GC contract for PyType_FromSpecWithBases

Change by Erlend E. Aasland : -- nosy: +erlendaasland ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44272] DeprecationWarning: The *random* parameter to shuffle() has been deprecated since Python 3.9 and will be removed in a subsequent version

Change by Steven D'Aprano : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue44263] Better explain the GC contract for PyType_FromSpecWithBases

Change by STINNER Victor : -- pull_requests: +25058 stage: resolved -> patch review pull_request: https://github.com/python/cpython/pull/26463 ___ Python tracker ___

[issue42213] Get rid of cyclic GC hack in sqlite3.Connection and sqlite3.Cache

Change by Erlend E. Aasland : -- pull_requests: +25057 pull_request: https://github.com/python/cpython/pull/26462 ___ Python tracker ___

[issue44263] Better explain the GC contract for PyType_FromSpecWithBases

STINNER Victor added the comment: I reopen the issue. I would prefer to change PyType_FromSpecWithBases() to raise an error if a type has the Py_TPFLAGS_HAVE_GC flag but its tp_traverse function is NULL. Oops, the Python stdlib has more types than only _ssl.SSLError with this error: *

[issue44229] Intermittent connection errors in ssl tests on macOS CI

Erlend E. Aasland added the comment: FWIW: 1st shell: $ ./python.exe -m test test_ssl -u all -m test_get_server_certificate -F $ ps [...] 1271 ttys0040:01.00 ./python.exe -m test test_ssl -u all -m test_get_server_certificate -F 2nd shell: $ sudo errinfo -p 1271 The syscall trace

[issue42972] [C API] Heap types (PyType_FromSpec) must fully implement the GC protocol

STINNER Victor added the comment: New changeset ff359d735f1a60878975d1c5751bfd2361e84067 by Miss Islington (bot) in branch '3.10': bpo-42972: Fix sqlite3 traverse/clear functions (GH-26452) (GH-26461) https://github.com/python/cpython/commit/ff359d735f1a60878975d1c5751bfd2361e84067

[issue44271] asyncio random carsh with longtime run

世界第一好吃 added the comment: I test it on OS :Windows 10 Pro x64 Python: 3.9.5 x64 This Code if work will it will print "are you ok" and stop. bug it print a random line like "done task 20897" ,stop print ,press Ctrl+C cannot break it. -- ___ Python

[issue42972] [C API] Heap types (PyType_FromSpec) must fully implement the GC protocol

STINNER Victor added the comment: New changeset d1124b09e8251061dc040cbd396f35ae57783f4a by Erlend Egeberg Aasland in branch 'main': bpo-42972: Fix sqlite3 traverse/clear functions (GH-26452) https://github.com/python/cpython/commit/d1124b09e8251061dc040cbd396f35ae57783f4a --

[issue42972] [C API] Heap types (PyType_FromSpec) must fully implement the GC protocol

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

[issue44271] asyncio random carsh with longtime run

Irit Katriel added the comment: What’s the output, what system are you using? -- nosy: +iritkatriel ___ Python tracker ___ ___

[issue44272] DeprecationWarning: The *random* parameter to shuffle() has been deprecated since Python 3.9 and will be removed in a subsequent version

Irit Katriel added the comment: What were you expecting? The documentation is here: https://docs.python.org/3/library/random.html -- nosy: +iritkatriel ___ Python tracker

[issue44272] DeprecationWarning: The *random* parameter to shuffle() has been deprecated since Python 3.9 and will be removed in a subsequent version

New submission from Kshitish Kumar : Code: import random as ran x = ran.shuffle(10,random=1) Output: DeprecationWarning: The *random* parameter to shuffle() has been deprecated since Python 3.9 and will be removed in a subsequent version. x = ran.shuffle(10,random=1) File

[issue11871] test_default_timeout() of test_threading.BarrierTests failure: BrokenBarrierError

Change by STINNER Victor : -- status: closed -> open ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue11871] test_default_timeout() of test_threading.BarrierTests failure: BrokenBarrierError

STINNER Victor added the comment: 10 years ago, the issue is not solved. Recent failure on AMD64 Windows8.1 Refleaks PR buildbot: https://buildbot.python.org/all/#/builders/470/builds/45 The issue started to make the buildbot fail since I added a threading.excepthook in libregrtest.

[issue44271] asyncio random carsh with longtime run

New submission from 世界第一好吃 : import asyncio import timeit num = 0 async def test(): global num num += 1 print(f"done task {num}") return f"task: {num}" async def main(): task = asyncio.create_task(test()) # ko = await test() # print(await task, ko) if __name__

[issue44271] asyncio random

Change by 世界第一好吃 : -- nosy: twbt4f priority: normal severity: normal status: open title: asyncio random ___ Python tracker ___ ___

[issue42972] [C API] Heap types (PyType_FromSpec) must fully implement the GC protocol

STINNER Victor added the comment: New changeset 4b20f2574d412f4c4a5b1ab799d8e71a5dd3b766 by Hai Shi in branch 'main': bpo-42972: Fully implement GC protocol for xxlimited (GH-26451) https://github.com/python/cpython/commit/4b20f2574d412f4c4a5b1ab799d8e71a5dd3b766 --

[issue42972] [C API] Heap types (PyType_FromSpec) must fully implement the GC protocol

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

[issue43964] ctypes CDLL search path issue on MacOS

Victor Lazzarini added the comment: Hi Ned, thanks for your detailed response. I have to say that the LD_LIBRARY_PATH partially worked in some cases, the library got loaded. However in cases where there were dependencies, further issues appeared particularly when the link (as revealed by

[issue44262] tarfile: some content different output

Vasco Gervasi added the comment: Yes, you can close it. For future reference: tar_reset = "/tmp/py_tar_reset.tar" def reset(tarinfo): tarinfo.uid = tarinfo.gid = 0 tarinfo.uname = tarinfo.gname = "root" tarinfo.mtime = 1 return tarinfo with tarfile.open(tar_reset, "w:xz")