[issue42737] PEP 563: drop annotations for complex assign targets

Change by Batuhan Taskaya : -- resolution: -> postponed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ _

[issue42737] PEP 563: drop annotations for complex assign targets

Batuhan Taskaya added the comment: Ah, seems like there is still one open PR. Keeping this up for that... -- resolution: postponed -> status: closed -> open ___ Python tracker __

[issue38530] Offer suggestions on AttributeError and NameError

Change by Dennis Sweeney : -- nosy: +Dennis Sweeney nosy_count: 8.0 -> 9.0 pull_requests: +24304 pull_request: https://github.com/python/cpython/pull/25584 ___ Python tracker _

[issue38530] Offer suggestions on AttributeError and NameError

Dennis Sweeney added the comment: I opened PR 25584 to fix this current behavior: >>> v Traceback (most recent call last): File "", line 1, in NameError: name 'v' is not defined. Did you mean: 'id'? >>> vv Traceback (most recent call last): File "", line 1, in NameError: name 'vv' is not

[issue43929] Raise on threading.Event.__bool__ due to ambiguous nature

Aritn Sarraf added the comment: Understood. Thanks both, for taking the time to look. -- ___ Python tracker ___ ___ Python-bugs-lis

[issue43888] GitHub Actions CI/CD `Coverage` job is broken on master

Batuhan Taskaya added the comment: Coverage runs are still failing on the master, and I think at least we should do something like allow failure or other wise github will send notifications for this flaky run. -- nosy: +BTaskaya ___ Python tracker

[issue43888] GitHub Actions CI/CD `Coverage` job is broken on master

Ammar Askar added the comment: For what it's worth I think Brett's suggestion of just removing the coverage build entirely is good too since it seems like no one actually looks at the results and they take up valuable CI time. -- nosy: +ammar2 ___

[issue14965] super() and property inheritance behavior

Victor Milovanov added the comment: There's a patch attached to this bug. Why is its stage "needs patch"? -- nosy: +Victor Milovanov ___ Python tracker ___ ___

[issue43918] anext builtin docstring has no signature text or info about default argument

Erik Welch added the comment: Thanks for taking a look Terry. I saw that error as well. It is separate from this issue, and I don't think it is a bug. No other builtin functions or methods that raise this error with this text have such a notice in their docstring, so it doesn't seem appro

[issue41486] Add _BlocksOutputBuffer for bz2/lzma/zlib module

Ma Lin added the comment: > The defines of BOB_BUFFER_TYPE/BOB_SIZE_TYPE/BOB_SIZE_MAX are ugly. If put > the core code together, these defines can be put in a thin wrapper in > _bz2module.c/_lzmamodule.c/zlibmodule.c files. I tried, it looks well. I will updated the PR within one or two days

[issue43876] argparse documentation contrasting nargs '*' vs. '+' is misleading

paul j3 added the comment: Let's see if I can clarify somethings. But first, I should say that I've worked with this code for so long, that I may miss things that could confuse a beginner. A basic distinction is between "optionals" and "positionals". I put those in quotes because that's n

[issue43892] Make match patterns explicit in the AST

Nick Coghlan added the comment: Interesting idea - I had missed that you were suggested "identifier*" for the cls node. It's simple enough to check for Name-or-Attribute in the AST validator though, and sticking with a standard expr_ty node means getting a lot of standard handling in the res

<    1   2