[issue44616] Incorrect tracing for "except" with variable

Change by Barry A. Warsaw : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue44613] Make importlib.metadata non-provisional in Python 3.10

Change by miss-islington : -- nosy: +miss-islington nosy_count: 2.0 -> 3.0 pull_requests: +25651 pull_request: https://github.com/python/cpython/pull/27106 ___ Python tracker _

[issue44613] Make importlib.metadata non-provisional in Python 3.10

Barry A. Warsaw added the comment: New changeset f6954cdfc50060a54318fb2aea4d80408381243a by Barry Warsaw in branch 'main': bpo-44613: Make importlib.metadata non-provisional (#27101) https://github.com/python/cpython/commit/f6954cdfc50060a54318fb2aea4d80408381243a -- _

[issue43950] Include column offsets for bytecode instructions

Pablo Galindo Salgado added the comment: New changeset 9c3eaf88dc5d5bed80cc45936de06b7b3162bc6d by Ammar Askar in branch 'main': bpo-43950: Add documentation for PEP-657 (GH-27047) https://github.com/python/cpython/commit/9c3eaf88dc5d5bed80cc45936de06b7b3162bc6d --

[issue44613] Make importlib.metadata non-provisional in Python 3.10

Barry A. Warsaw added the comment: New changeset 7223ce3b3f50ec8a825e317437ea0359b6ad6856 by Miss Islington (bot) in branch '3.10': bpo-44613: Make importlib.metadata non-provisional (GH-27101) (#27106) https://github.com/python/cpython/commit/7223ce3b3f50ec8a825e317437ea0359b6ad6856 --

[issue44613] Make importlib.metadata non-provisional in Python 3.10

Change by Barry A. Warsaw : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ _

[issue44613] Make importlib.metadata non-provisional in Python 3.10

Barry A. Warsaw added the comment: Jason, I think the question you raise re: accelerated deprecation, is probably a RM or SC question. I'll nosy in Pablo and see if he has a strong opinion. -- nosy: +pablogsal ___ Python tracker

[issue44611] CPython uses deprecated randomness API

Dan Stromberg added the comment: Yes, cng-portal. On Mon, Jul 12, 2021 at 3:24 PM Thomas Grainger wrote: > > Thomas Grainger added the comment: > > https://docs.microsoft.com/en-us/windows/win32/seccng/cng-portal ? > > -- > nosy: +graingert > > __

[issue44603] REPL: exit when the user types exit instead of asking them to explicitly type exit()

Steven D'Aprano added the comment: Please don't do this. On Mon, Jul 12, 2021 at 02:19:58PM +, Pablo Galindo Salgado wrote: > >>> exit > bye! This is a user-hostile and unfriendly UI for Python. The Python REPL is not a shell like bash etc, it should be safe to evaluate any builtin obj

[issue44603] REPL: exit when the user types exit instead of asking them to explicitly type exit()

Steven D'Aprano added the comment: > Other than that, only arguments based on the purity of the language, > but I think having this working is far more important. Having this "working" is not important at all. This is precisely the sort of user-hostile anti-feature that we should avoid, not

[issue44603] REPL: exit when the user types exit instead of asking them to explicitly type exit()

Pablo Galindo Salgado added the comment: Thanks Steven for your input and your comments and for expressing your concerns. I will hold the PR then until there is consensus on how to proceed and all concerns are addressed (eventually closing it if there isn't consensus). I'm any case, I think

[issue44616] Incorrect tracing for "except" with variable

Pablo Galindo Salgado added the comment: Marking as release blocker for the first release candidate. Ned, I assume this comes from some recent bug report in coverage, but it would be great if you could ask your users to test the latest beta and report any issue before we release the first ca

[issue44616] Incorrect tracing for "except" with variable

Pablo Galindo Salgado added the comment: I assume this is due to some artificial bytecode for cleaning the variable in the exception -- ___ Python tracker ___ ___

[issue44603] REPL: exit when the user types exit instead of asking them to explicitly type exit()

Stargirl Flowers added the comment: @steven.daprano I appreciate your perspective but you laid out a lot of strong opinions as if they're incontrovertible truths. The motivation here isn't laziness- I created this bug because I saw actual people across various skill levels that are bugged by

[issue44616] Incorrect tracing for "except" with variable

Barry A. Warsaw added the comment: Pablo, this is triggered by my bug report here: https://github.com/nedbat/coveragepy/issues/1187 I tested this again today with the 3.10 git head and still got the coverage misses. Happy to try any other combinations. -- _

[issue44603] REPL: exit when the user types exit instead of asking them to explicitly type exit()

Taylor Alexander added the comment: Am I correct in thinking that the proposed change only affects the use case where a user types exit in to the REPL and hits return? And that any other case is unaffected? I can only imagine that the majority of users who type exit in to the interpreter ar

[issue44602] Issue with get_build_version in msvc9compiler.py in distutils

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

[issue44608] Memory use increase in function _tkinter._flatten

Change by Ned Deily : -- components: +Tkinter ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue44617] Undesired Behavior on `match` using Singleton object

New submission from Pablo Aguilar : Hey, I'm not sure if this is really a bug but I'd like to show to prevent some undesired behavior! I'm working in the `match` support for returns (https://github.com/dry-python/returns) library when I saw a behavior similar to the described in `Constant Va

[issue42958] filecmp.cmp(shallow=True) isn't actually shallow when only mtime differs

Christof Hanke added the comment: Andrei, cmp is the deep-compare part of filecmp. I thought we were taking about the shallow one. Thus, - shallow like rsync "quick": size + mtime. - deep like cmp -- ___ Python tracker

[issue44603] REPL: exit when the user types exit instead of asking them to explicitly type exit()

Vedran Čačić added the comment: > based on feedback it seems that almost everyone expects "exit" to exit I don't, and I don't remember being asked. Let me be clear: if exit were a Python keyword, then maybe I would expect that. Or at least, I could convince myself to expect that. But exit is

[issue44603] REPL: exit when the user types exit instead of asking them to explicitly type exit()

Change by Stargirl Flowers : -- resolution: -> rejected stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Pytho

[issue44608] Memory use increase in function _tkinter._flatten

Change by Serhiy Storchaka : -- keywords: +patch nosy: +serhiy.storchaka nosy_count: 1.0 -> 2.0 pull_requests: +25652 stage: -> patch review pull_request: https://github.com/python/cpython/pull/27107 ___ Python tracker

[issue44608] Memory use increase in function _tkinter._flatten

Serhiy Storchaka added the comment: Thank you for your report stardust222. Indeed, there is a leak if an argument is a sequence or set, but not list or tuple. PR 27107 fixes it. -- components: +Extension Modules -C API, Tkinter versions: +Python 3.10, Python 3.11

[issue44617] Undesired Behavior on `match` using Singleton object

Dennis Sweeney added the comment: This code... match my_maybe: case Maybe.empty: print('FIRST CASE') case _: print('DEFAULT CASE') ... is roughly equivalent to this code: if my_maybe == Maybe.empty: print('FIRST CASE') case _:

[issue44606] Discrepancy between isinstance() and issubclass() for union types

Serhiy Storchaka added the comment: I have found this when refactored the code of Objects/unionobject.c. So I have a patch which fixes this, but I want to make sure what behavior is considered correct. -- ___ Python tracker

[issue44597] Poll returns POLLOUT on Pipe read endpoint on MacOS 10.14

Ronald Oussoren added the comment: Without having looked at this issue in detail... This looks like an issue with macOS and not Python. In general API's providing access to system calls are just thin wrappers around those system calls. If this is a bug in macOS there's nothing we can do abo

<    1   2