[issue18766] IDLE: Autocomplete in editor doesn't work for un-imported modules

Terry J. Reedy added the comment: The import-on-demand would be executed in the Shell's execution process namespace, so it works with the current implementation. I said above that this puts names 'where they don't belong', but I feel a little differently now. A variant idea might be to

[issue18766] IDLE: Autocomplete in editor doesn't work for un-imported modules

Change by Thrlwiti : -- nosy: -THRlWiTi ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue18766] IDLE: Autocomplete in editor doesn't work for un-imported modules

Tal Einat added the comment: I propose closing this as "wontfix", since this goes strongly against how completions currently work in IDLE (based on the namespace of the shell), and I don't think we're considering changing that. -- nosy: +taleinat

[issue18766] IDLE: Autocomplete in editor doesn't work for un-imported modules

Terry J. Reedy added the comment: The concern about adding bugs could be alleviated by checking whether the name is in an import statement. But it still might not be in the proper form. I am trying to reduce the run.py import to those actually needed in run.py. I already reduced sys.modules

[issue18766] IDLE: Autocomplete in editor doesn't work for un-imported modules

Terry J. Reedy added the comment: I opened #27609 to keep track of multiple completion issues. Some additions to what I said above. 1. I would like to move the actual fetch code to run.py, since it is normally executed in the user process. See #27534, but also below. 2. Idle currently

[issue18766] IDLE: Autocomplete in editor doesn't work for un-imported modules

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___

[issue18766] IDLE: Autocomplete in editor doesn't work for un-imported modules

Changes by irdb : -- nosy: +irdb ___ Python tracker ___ ___ Python-bugs-list mailing

[issue18766] IDLE: Autocomplete in editor doesn't work for un-imported modules

Terry J. Reedy added the comment: This issue is about name completion and not path completion. I have re-reviewed the patch, current code, current behavior, and the fetch_completions doctstring that more or less explains why name completion cannot reliably work given how Idle now works. I

[issue18766] IDLE: Autocomplete in editor doesn't work for un-imported modules

Saimadhav Heblikar added the comment: Hi Terry, Would it be better if the current inlined code is moved into get_entity? It will also make it easier to test. The try:... except ImportError block be present within the get_entity method itself? Otherwise, I will make a patch on what you said

[issue18766] IDLE: Autocomplete in editor doesn't work for un-imported modules

Changes by Saimadhav Heblikar saimadhavhebli...@gmail.com: -- nosy: +sahutd ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18766 ___ ___

[issue18766] IDLE: Autocomplete in editor doesn't work for un-imported modules

Mark Lawrence added the comment: The patch is simple but I don't know enough about IDLE to comment technically, what do you think Terry? -- nosy: +BreamoreBoy versions: +Python 3.4, Python 3.5 -Python 3.3 ___ Python tracker rep...@bugs.python.org

[issue18766] IDLE: Autocomplete in editor doesn't work for un-imported modules

Terry J. Reedy added the comment: A least a manual (human) test is needed: a description of steps that do not work now and do work with a patch. Currently, get_entity() is only called in one place in fetch_completions; it is not used anywhere else in idlelib. (Call_tips defines another

[issue18766] IDLE: Autocomplete in editor doesn't work for un-imported modules

New submission from Phil Webster: If you open a new editor window in IDLE, some modules will autocomplete (re, os, other common modules used by IDLE) and others will not (textwrap, datetime, ...). The current solution is to run your module or type the imports into the shell window to get