[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

[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

[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

[issue44608] Memory use increase in function _tkinter._flatten

Change by Ned Deily : -- components: +Tkinter ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[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 ___

[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

[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()

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

[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 ___

[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

[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

[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()

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

[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 > >

[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

[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: 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

[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 f6954cdfc50060a54318fb2aea4d80408381243a by Barry Warsaw in branch 'main': bpo-44613: Make importlib.metadata non-provisional (#27101) https://github.com/python/cpython/commit/f6954cdfc50060a54318fb2aea4d80408381243a --

[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

[issue44616] Incorrect tracing for "except" with variable

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

[issue34451] docs: tutorial/introduction doesn't mention toggle of prompts

Change by Thomas : -- keywords: +patch nosy: +thmsdnnr nosy_count: 6.0 -> 7.0 pull_requests: +25650 stage: -> patch review pull_request: https://github.com/python/cpython/pull/27105 ___ Python tracker

[issue44616] Incorrect tracing for "except" with variable

Ned Batchelder added the comment: Based on https://github.com/nedbat/coveragepy/issues/1187, btw -- ___ Python tracker ___ ___

[issue44616] Incorrect tracing for "except" with variable

New submission from Ned Batchelder : This construct isn't traced properly: except ExceptionName as var: if something: raise Here's a reproducer: -- 8< - import linecache, sys def trace(frame, event, arg): # The weird globals here

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

Andrei Kulakov added the comment: But rsync is a quite more specific tool. For example, unix cmp command does not guess based on any part of `stat` sig. That's a much closer command in scope to 'filecmp'. -- ___ Python tracker

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

Christof Hanke added the comment: Hi Andrei, I would follow rsync. >From the man page: """ [...] -c, --checksum This changes the way rsync checks if the files have been changed and are in need of a transfer. Without this option, rsync uses a "quick check"

[issue44611] CPython uses deprecated randomness API

Thomas Grainger added the comment: https://docs.microsoft.com/en-us/windows/win32/seccng/cng-portal ? -- nosy: +graingert ___ Python tracker ___

[issue44611] CPython uses deprecated randomness API

Tim Peters added the comment: Dan, the Microsoft URL in your message gives a 404 for me. Did you perhaps mean to end it with "cng-portal" (instead of "cng-por")? -- nosy: +tim.peters ___ Python tracker

[issue44615] Multiprocessing Pool example and comments incomplete/wrong?

New submission from Florian Streibelt : The docs at the url https://docs.python.org/3/library/multiprocessing.html#module-multiprocessing.pool state in a red warning box: "Warning multiprocessing.pool objects have internal resources that need to be properly managed (like any other

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

Jason R. Coombs added the comment: Thanks Barry for filing this. I was planning to do it but happy for you to beat me to it. I had one question I'd been meaning to ask - with this change, can the code paths that were deprecated in 3.10 be removed in 3.11 (SelectableGroups and cast to dict

[issue44614] Broken Pipe in Server of Manager in multiprocessing when finalizing, sometimes

New submission from Florian Streibelt : It seems that the shutdown() method of the Server in in managers.py is already sending the result of its execution directly into the connection, and then the handle_request() method is trying to send ('#RETURN', None) yet again after returning from the

[issue38825] shutil.disk_usage - Lacking documentation

Norman Lorrain added the comment: Something like this: .. impl-detail:: Where applicable (e.g. Unix) *path* must point to somewhere on a **mounted** filesystem partition. On Sun, 11 Jul 2021 at 16:18, Tyler Crompton wrote: > > Tyler Crompton added the comment: > > Not even the

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

Andrei Kulakov added the comment: Also see this 16 years old issue: https://bugs.python.org/issue1234674 -- ___ Python tracker ___

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

Guido van Rossum added the comment: Ken Jin, should we treat type(None) as a subclass of int|None? -- nosy: +kj ___ Python tracker ___

[issue44593] _randbelow_with_getrandbits may request an unnecessary random bit

Change by Mark Dickinson : -- resolution: -> duplicate superseder: -> _randbelow_with_getrandbits function inefficient with powers of two ___ Python tracker ___

[issue10716] Modernize pydoc to use better HTML and separate CSS

Éric Araujo added the comment: On second thought, this issue is not purely programming, but also has a UI component. Better HTML and separated CSS would be good, but before that I think we’d need someone with design chops to mock up a better page layout and style (better than big coloured

[issue10716] Modernize pydoc to use better HTML and separate CSS

Éric Araujo added the comment: Someone would need to take the patch, apply it to current main branch, fix issues and open a PR. -- versions: +Python 3.11 -Python 3.8 ___ Python tracker

[issue43950] Include column offsets for bytecode instructions

Pablo Galindo Salgado added the comment: New changeset 1890dd235f618d60c938f6904d2e1a8a56f99c1c by Batuhan Taskaya in branch 'main': bpo-43950: Specialize tracebacks for subscripts/binary ops (GH-27037) https://github.com/python/cpython/commit/1890dd235f618d60c938f6904d2e1a8a56f99c1c

[issue44612] inspect module points that could be using f-String

Eric V. Smith added the comment: Yes, thank you Leonardo! There are probably places in the stdlib where changing to f-strings would be a performance improvement. Of course finding those places is the challenge! -- nosy: +eric.smith ___ Python

[issue44605] functools.total_ordering doesn't work with metaclasses

Dennis Sweeney added the comment: The one twist is that if type(b) is a strict subtype of type(a), then "a < b" first calls type(b).__gt__(b, a), then falls back to type(a).__lt__(a, b). Example: >>> class Int(int): ... def __gt__(self, other): ... print("Here!") ...

[issue44612] inspect module points that could be using f-String

Leonardo Freua added the comment: Thanks, Ammar. I'll look. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue44612] inspect module points that could be using f-String

Ammar Askar added the comment: Thanks for trying to help Leonardo! You might consider looking for easy issues on the bug tracker or reviewing open pull requests to help. Definitely take a look at the dev guide :) https://cpython-devguide.readthedocs.io/fixingissues/ -- resolution:

[issue44612] inspect module points that could be using f-String

Leonardo Freua added the comment: Understood. Anyway, it was good to try to help at this point. -- ___ Python tracker ___ ___

[issue44600] match/case statements trace incorrectly in 3.10.0b4

Ammar Askar added the comment: Brandt, maybe this regression test from a previous tracing bug might be useful for the test writing: https://github.com/python/cpython/pull/22026/files#diff-8b73bfc55514d8add8904c5f4d1d24b7b644ebfccba8d846085303577aa94dd6 -- nosy: +ammar2

[issue44612] inspect module points that could be using f-String

Ammar Askar added the comment: As per https://bugs.python.org/issue36249 and https://bugs.python.org/issue38351 We don't generally do large-scale changes that are mostly formatting based. We would prefer that these sort of improvements happen when someone happens to be touching that code

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

Change by Barry A. Warsaw : -- keywords: +patch pull_requests: +25649 stage: -> patch review pull_request: https://github.com/python/cpython/pull/27101 ___ Python tracker ___

[issue44612] inspect module points that could be using f-String

Change by Leonardo Freua : -- keywords: +patch pull_requests: +25648 stage: -> patch review pull_request: https://github.com/python/cpython/pull/27100 ___ Python tracker ___

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

New submission from Barry A. Warsaw : As discussed with Jason, importlib.metadata will be made non-provisional in 3.10. I have a PR in the works for this. -- assignee: barry components: Documentation messages: 397344 nosy: barry, jaraco priority: normal severity: normal status: open

[issue44612] inspect module points that could be using f-String

New submission from Leonardo Freua : There are some points in inspect module (I counted 48 since version 3.7) that could be using f-String formatting instead of format(). Changing these points will improve code readability, it will also decrease the complexity at these points and not to

[issue44610] Format issue with strftime and %Y

Change by Bartosz Kaznowski : -- versions: +Python 3.10, Python 3.6, Python 3.7, Python 3.8 ___ Python tracker ___ ___

[issue44610] Format issue with strftime and %Y

Change by Bartosz Kaznowski : -- versions: +Python 3.9 -Python 3.7 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue44559] Enum: revert to 3.9

Change by Ethan Furman : -- pull_requests: +25647 pull_request: https://github.com/python/cpython/pull/27099 ___ Python tracker ___

[issue43299] pyclbr.readmodule_ex traversing "import __main__": dies with ValueError: __main__.__spec__ is None / is not set

Andrei Kulakov added the comment: Upon further pondering, I'm not sure PyWin is doing the right thing here. I believe it's best to first file it with PyWin and find out what it is trying to do and why. Pyclbr behavior sort of makes sense to me -- pyclbr goal is to parse and browse the

[issue44607] Teleport method for turtle class

Muffinlicious added the comment: Turtle is the most accessible and well-known drawing module for kids to use so teleporting makes more sense in the context of drawing random shapes or small pictures around the screen. I've seen the penup/goto/pendown combo so often that I figure it at

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

Andrei Kulakov added the comment: Christof and Alexander, as you both said your preference is to have some way of enforcing "only shallow" compare, I want to clarify -- it seems if you do that, you will get the answer of True if the files are most likely the same (sig is equal), but if the

[issue44611] CPython uses deprecated randomness API

New submission from Dan Stromberg : CPython 3.9 uses CryptGenRandom(), which has been deprecated by Microsoft. I'm told the randomness produced by CryptGenRandom() is fine, but Microsoft has introduced a newer API for getting randomness. For these reasons, Python/bootstrap_hash.c should be

[issue44571] itertools: takedowhile()

pavel-lexyr added the comment: Thank you - that answers the questions. The use case where we would want to know if the last element is transitional or not completely slipped my mind for some reason. -- ___ Python tracker

[issue44571] itertools: takedowhile()

Tim Peters added the comment: That said, if you really do want those semantics, it's easy to build on top of Raymond's API: def takewhile_plus_one_more_if_any(pred, iterable): from itertools import islice, chain before, after = before_and_after(pred, iterable) return

[issue44428] _ProactorBasePipeTransport.abort() after _ProactorBasePipeTransport.close() does not cancel writes

Change by Thomas Grainger : -- nosy: +lukasz.langa ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44571] itertools: takedowhile()

Tim Peters added the comment: If you don't use the 'after` iterator, then of course you'll never see the values (if any) it would have yielded. How could it possibly be otherwise? By design and construction, the `before` iterator ends before yielding the first (if any) transitional element.

[issue42194] Docs for argparse.BooleanOptionalAction missing "New in version 3.9"

Change by Łukasz Langa : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue42194] Docs for argparse.BooleanOptionalAction missing "New in version 3.9"

Łukasz Langa added the comment: New changeset c786988b19d7b6808d4c940f7206b95e49e06b71 by Miss Islington (bot) in branch '3.9': bpo-42194: Add "New in version: 3.9" to argparse.BooleanOptionalAction (GH-23026) (#27098)

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

Pablo Galindo Salgado added the comment: Since Paul is +1 if another core dev (or devs) are +1 as well with the approach in PR27096 I would feel confident to proceed with this. Alternatively, we could discuss this more generally in python-dev if someone feels that we should have a more open

[issue43048] Printing RecursionError results in RecursionError

Change by Łukasz Langa : -- stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list

[issue43048] Printing RecursionError results in RecursionError

Łukasz Langa added the comment: New changeset 489c27358376e772a61753c3f67daa836ca1eab7 by Vladimir Feinberg in branch '3.9': [3.9] bpo-43048: RecursionError traceback RecursionError bugfix for cpy3.9 (GH-24460) (#24460)

[issue42194] Docs for argparse.BooleanOptionalAction missing "New in version 3.9"

Łukasz Langa added the comment: New changeset 721d4796be60e6a0a11dee8318794f78928648c1 by Miss Islington (bot) in branch '3.10': bpo-42194: Add "New in version: 3.9" to argparse.BooleanOptionalAction (GH-23026) (#27097)

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

Pablo Galindo Salgado added the comment: > Are there any downsides to doing it this way? It seems tightly scoped and > with minimal overhead. We also need to support quit(), if we go this route. It makes parsing in the REPL a bit slower because it needs to check for this at every command

[issue43299] pyclbr.readmodule_ex traversing "import __main__": dies with ValueError: __main__.__spec__ is None / is not set

Andrei Kulakov added the comment: Actually, I was mistaken about this, `readmodule_ex` can get the __main__ from sys.modules.. I will look more into this later today. -- ___ Python tracker

[issue44610] Format issue with strftime and %Y

New submission from Bartosz Kaznowski : When you convert a date pre the year 1000 to a string with `%Y` as the formatter and then back to a date again then it fails. This is because `%Y` expects it to be formatted with leading zeroes. For example, the year 1/01/01 (/mm/dd) should be

[issue26329] os.path.normpath("//") returns //

Change by Łukasz Langa : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue26329] os.path.normpath("//") returns //

Łukasz Langa added the comment: New changeset 47abf240365ddd54a91c6ac167900d4bf6806c4f by Miss Islington (bot) in branch '3.9': bpo-26329: update os.path.normpath documentation (GH-20138) (#27095) https://github.com/python/cpython/commit/47abf240365ddd54a91c6ac167900d4bf6806c4f --

[issue42194] Docs for argparse.BooleanOptionalAction missing "New in version 3.9"

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

[issue42194] Docs for argparse.BooleanOptionalAction missing "New in version 3.9"

Łukasz Langa added the comment: New changeset da2e673c53974641a0e13941950e7976bbda64d5 by David Sanders in branch 'main': bpo-42194: Add "New in version: 3.9" to argparse.BooleanOptionalAction (GH-23026) https://github.com/python/cpython/commit/da2e673c53974641a0e13941950e7976bbda64d5

[issue42194] Docs for argparse.BooleanOptionalAction missing "New in version 3.9"

Change by miss-islington : -- nosy: +miss-islington nosy_count: 9.0 -> 10.0 pull_requests: +25645 pull_request: https://github.com/python/cpython/pull/27097 ___ Python tracker

[issue43207] InspectLoader.is_package is not an abstract method

Change by Łukasz Langa : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue38820] Make Python compatible with OpenSSL 3.0.0

Łukasz Langa added the comment: New changeset c92b391dcefe9a7b3e6290bc2e2356eedfcf4bc3 by Christian Heimes in branch '3.9': [3.9] bpo-38820: Test with OpenSSL 3.0.0-alpha16 (GH-25942) (#25944) https://github.com/python/cpython/commit/c92b391dcefe9a7b3e6290bc2e2356eedfcf4bc3 -- nosy:

[issue43207] InspectLoader.is_package is not an abstract method

Łukasz Langa added the comment: New changeset 779983ed7f86610be4a7201deeffdcb8608977e0 by Miss Islington (bot) in branch '3.9': bpo-43207: InspectLoader.is_package is not an abstract method (GH-24517) (#26322) https://github.com/python/cpython/commit/779983ed7f86610be4a7201deeffdcb8608977e0

[issue43298] Windows build cannot detect missing Windows SDK

Łukasz Langa added the comment: New changeset e7009f4f9a6a55036ef628a07bedc8dab1aa851e by Miss Islington (bot) in branch '3.9': bpo-43298: Improved error message when building without the Windows SDK installed (GH-26800) (#26803)

[issue44472] ltrace functionality doesn't work if there is an exception set

Łukasz Langa added the comment: New changeset 6fb4248cd9502f50dd089fdcf548d735dcfd981e by Miss Islington (bot) in branch '3.9': bpo-44472: Fix ltrace functionality when exceptions are raised (GH-26822) (#26831) https://github.com/python/cpython/commit/6fb4248cd9502f50dd089fdcf548d735dcfd981e

[issue44022] urllib http client possible infinite loop on a 100 Continue response

Łukasz Langa added the comment: New changeset 0389426fa4af4dfc8b1d7f3f291932d928392d8b by Miss Islington (bot) in branch '3.8': bpo-44022: Improve the regression test. (GH-26503) (#26506) https://github.com/python/cpython/commit/0389426fa4af4dfc8b1d7f3f291932d928392d8b --

[issue26329] os.path.normpath("//") returns //

Łukasz Langa added the comment: New changeset 443db64f496d3988d20cfda2c3c2ceb6702df36f by Miss Islington (bot) in branch '3.10': bpo-26329: update os.path.normpath documentation (GH-20138) (GH-27094) https://github.com/python/cpython/commit/443db64f496d3988d20cfda2c3c2ceb6702df36f

[issue44609] Buffer support in the stable ABI

New submission from Tarun Johar : PEP 384 and PEP 652 define a stable ABI to be used with Python 3.2 and later. On Windows, symbols for the stable ABI are exported from the python3.dll shared library. The following functions are present in Python 3.9 but have been removed from Python

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

Christof Hanke added the comment: Hi, this is also discussed in https://bugs.python.org/issue41354. Ciao, Christof -- nosy: +chanke ___ Python tracker ___

[issue41354] filecmp.cmp documentation does not match actual code

Christof Hanke added the comment: Andrei, See https://bugs.python.org/issue42958 Someone else stumbled over this topic. Maybe you can merge these two requests? Otherwise, I'm fine with a new arg. Christof -- ___ Python tracker

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

Paul Ganssle added the comment: I'm +1 for Pablo's approach. That's approximately what I meant by "special-case it in the REPL layer" anyway. Are there any downsides to doing it this way? It seems tightly scoped and with minimal overhead. -- ___

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

Stargirl Flowers added the comment: Fair point about semantic behavior and complexity, but hopefully we can come up with a solution that's easier for users. I do like the PR suggested. -- ___ Python tracker

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

Pablo Galindo Salgado added the comment: > I do want to be cautious of saying that we can't do it because of the way the > REPL is currently implemented- which appears to be an implementation driven > by convenience more than necessity. Apologies if I have not been clear on this. Is not

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

Stargirl Flowers added the comment: I do want to be cautious of saying that we can't do it because of the way the REPL is currently implemented- which appears to be an implementation driven by convenience more than necessity. I also find pushing against special-case behavior in the REPL

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

Pablo Galindo Salgado added the comment: One thing we *could* do which is not super invasive, is to match a single AST node of type NAME at the end of Python run. This seems to work but is a bit inelegant: >>> print(exit) Use exit() or Ctrl-D (i.e. EOF) to exit >>> [exit] [Use exit() or

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

Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +25644 stage: -> patch review pull_request: https://github.com/python/cpython/pull/27096 ___ Python tracker

[issue44571] itertools: takedowhile()

pavel-lexyr added the comment: There is a core part of the `takedowhile` proposal's use case that I am having trouble envisioning via the alternative `before_and_after` proposal. If the `after` part of the iterator the user does not engage with, the transitional elements will be stuck

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

Pablo Galindo Salgado added the comment: > would be in the REPL layer by special-casing `exit` Unfortunately, there is no REPL *layer* as my previous comments mentioned. There is a few details that change for interactive mode but fundamentally the pipeline is the same as reading from a

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

Paul Ganssle added the comment: If we want to confine the behavior to just the repl, we could possibly have the repl set an environment variable or something of that nature for interactive sessions, so that `__repr__` of `exit` can tell the difference between being invoked in a REPL and not

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

Pablo Galindo Salgado added the comment: For reference, IPython has an entire interception + filtering mechanism to auto call certain functions: https://github.com/ipython/ipython/blob/0e4d6390b2174fb1b352a082b72ad387ae696e87/IPython/core/prefilter.py#L414-L425 where exit is one instance of

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

Pablo Galindo Salgado added the comment: IPython and other reprs are an entire abstraction layer on top of Python, which allows them to do a lot of extra things like implement new commands and alters a lot of behaviours, but the CPython REPL is just the interpreter evaluating commands, and

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

Pablo Galindo Salgado added the comment: > However, I disagree that "exit" should not be a special case. But a special case of *what*? How would you implement this in a backwards-compatible way? -- ___ Python tracker

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

Stargirl Flowers added the comment: Also, if a PEP is recommended, I will be happy to author it. -- ___ Python tracker ___ ___

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

Stargirl Flowers added the comment: I don't think we should completely write off the possibility of doing this just because the *current* implementation is counter-intuitive. As I expressed in the original post, the explanation of this behavior is rather unsatisfying to newcomers. Also

[issue26329] os.path.normpath("//") returns //

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

[issue26329] os.path.normpath("//") returns //

Joannah Nanjekye added the comment: New changeset 66c5853406bbcccecf35372795078c0641a5f385 by Furkan Onder in branch 'main': bpo-26329: update os.path.normpath documentation (GH-20138) https://github.com/python/cpython/commit/66c5853406bbcccecf35372795078c0641a5f385 --

  1   2   >