[issue43654] IDLE: Applying settings disables tab completion

Change by Tal Einat : -- pull_requests: +25016 pull_request: https://github.com/python/cpython/pull/26421 ___ Python tracker ___

[issue43654] IDLE: Applying settings disables tab completion

Terry J. Reedy added the comment: Tal, I think you had the right solution the first time. To me, tab is (should be) a fixed key, and the event added just once, like the other fixed keys. I am quite surprised that it isn't. Please revise or make a new patch to remove it from both

[issue43654] IDLE: Applying settings disables tab completion

Change by Tal Einat : -- versions: +Python 3.11, Python 3.9 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43654] IDLE: Applying settings disables tab completion

Tal Einat added the comment: Indeed, adding the events bound in EditorWindow.__init__ to RemoveKeybindings() and ApplyKeybindings(), so they are bound in the correct order, resolves this issue. See PR GH-26403. -- ___ Python tracker

[issue43654] IDLE: Applying settings disables tab completion

Change by Tal Einat : -- keywords: +patch pull_requests: +24996 stage: test needed -> patch review pull_request: https://github.com/python/cpython/pull/26403 ___ Python tracker

[issue43654] IDLE: Applying settings disables tab completion

Tal Einat added the comment: The original issue appears to be caused by <> also being bound to Tab, but <> only being bound using event_add() once in EditorWindow.__init__(). Therefore, RemoveKeybindings() does remove the binding for tab due to <>, but <> is not bound again by

[issue43654] IDLE: Applying settings disables tab completion

Mikhail added the comment: I also checked this behavior in Jython and IPython, and there errors are explicitly caused when putting/calling such values (I also checked on MicroPython online version, everything just hangs there). For IPython I created an issue on their Github, I'm thinking of

[issue43654] IDLE: Applying settings disables tab completion

Terry J. Reedy added the comment: I presume '^' means 'hit Tab'. The underlying Python problem is that namespaces are conceptually mappings of names (identifiers), a subset of strings, to objects. Python specifies that the global namespace is a dict, which I believe could mean a dict

[issue43654] IDLE: Applying settings disables tab completion

Mikhail added the comment: I did a little experiment, and it turned out that the problem is not in the IDLE, but inside Python itself. With this case, the same behavior remains inside the terminal version of Python, and IPython also produces a similar error. --

[issue43654] IDLE: Applying settings disables tab completion

Mikhail added the comment: Hello again! I found another kind of bug, where the autosupplement window doesn't show up. In order for the bug to occur, you need to put a non-string value into `locals()`. Example: ``` locals()['arg'] = 123 # or locals().setdefault('arg', 123) # ^ it's okay

[issue43654] IDLE: Applying settings disables tab completion

Terry J. Reedy added the comment: Investigation of this issue is complicated by the fact that the editor test widgets are wrapped by multicall.MulticallCreator. It intercepts bind and event method calls (other than event_generate) for user pseudoevents. It keeps its own map of pseudoevent

[issue43654] IDLE: Applying settings disables tab completion

Change by Mikhail : -- nosy: +tetelevm ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43654] IDLE: Applying settings disables tab completion

New submission from Terry J. Reedy : (Original report by Mikhail on #43647, running 3.9 on Linux; verified and extended by me running 3.10 on Windows.) Normally, "i" brings up a completion window with 'id', 'if', 'import', etc. Opening a Settings windows with Options => Configure IDLE and