-
-
Notifications
You must be signed in to change notification settings - Fork 784
Fail to use autocompletion in python console #15872
Copy link
Copy link
Closed
Labels
bug/regressionp3https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Milestone
Metadata
Metadata
Assignees
Labels
bug/regressionp3https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Background:
between python version 3.7 and 3.11, change was made by python developers in rlcompleter module, which removed exception handling from attr_match method which was previously suppressing some type of exceptions.
Steps to reproduce:
Actual behavior:
Different types of exceptions are thrown
Expected behavior:
Autocompletion should work as expected without throwing exceptions
NVDA logs, crash dumps and other attachments:
ERROR - unhandled exception (00:57:28.295) - MainThread (11340):
Traceback (most recent call last):
File "pythonConsole.pyc", line 410, in onInputChar
File "pythonConsole.pyc", line 335, in complete
File "pythonConsole.pyc", line 358, in _getCompletions
File "rlcompleter.pyc", line 92, in complete
File "rlcompleter.pyc", line 189, in attr_matches
File "baseObject.pyc", line 62, in get
File "baseObject.pyc", line 168, in getPropertyViaCache
File "NVDAObjects\IAccessible_init.pyc", line 1052, in _get_labeledBy
TypeError: cannot unpack non-iterable NoneType object
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
alpha-30120,8052b68f
Windows version:
Windows 11 23H2 (AMD64) build 22631.2715
Name and version of other software in use when reproducing the issue:
None
Other information about your system:
Other questions
Does the issue still occur after restarting your computer?
Not applicable
Have you tried any other versions of NVDA? If so, please report their behaviors.
Only applicable to python 3.11 version of nvda
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Not applicable