Importing from __main__ should cause auto completion like normal imports

[mathgeniuszach]

Seeing a from __main__ import <module> statement should attempt to grab rich auto-completion data in the same way as if import <module> was called. Or at least, it should be an option as modules in __main__ can be imported under any name unknown to the current script.

I was writing a python based executable with external modules that grab standard python modules from __main__ (so people don't need to install python in order to run the executable's modules), and noticed I do not get module auto-completion in the same way as if I would just use the statement import <module>.

[brettcannon]

Which language server are you using? And are you saying you named a package __main__? If so then that's actually going to have some unforeseen consequences with Python itself as the __main__ name has special meaning and is expected to be a (sub)module, not a package.

[mathgeniuszach]

I was using the default settings, so the language server I was using was "Jedi", though switching out both language servers and linters (I installed and tried every python linter available) seems to either complain about __main__ being either unresolved or non-existent.

And no, I know not to name a package __main__. I have a main script (not named __main__) that imports a bunch of modular python scripts from a folder next to the script, and those modular python scripts import packages from the main script through __main__ (with the use of the __import__() function), so imports work properly when the main script gets compiled to an executable but the modular scripts don't.

For example, I have the statement import fpclib in the main script (as well as a calls to __import__() to import all modular scripts), then I import the package into a modular script with from __main__ import fpclib. typing fpclib. gives auto-completion in the main script, but not in any of the modular scripts. I suppose what I'm asking for is an override setting so that importing from unresolved __main__ attempts to gather auto-completion data as if the from __main__ part does not exist. Perhaps I should be posting this elsewhere.

Perhaps I should provide the related lines of code because the project is on GitHub:
Call to import modular scripts
Example modular script

[brettcannon]

I see what you're doing now. Yeah, definitely don't import __main__; it isn't doing what you think it does and it will cause you trouble later on. It's best to directly import the module you want to work with by its actual name. And there's no way for auto-completion to be provided for __main__ in your case anyway because we don't know what __main__ is (you can only know when code executes and that's not how auto-complete is provided).

I also wouldn't call __import__() directly; use importlib.import_module() instead which is much easier to work with and will work the way you expect (__import__() is designed for Python's internal user, not human beings 😉 ).

And just so you know, I implemented import, so this isn't coming from some random crank on the internet. 😄

[mathgeniuszach]

Thanks, didn't realize I could just utilize normal import statements in the modular scripts... though thinking about it sys.path should be the same for the main script and imported modules, so I guess it makes sense how they both can import from the packaged libraries within the executable directly. That kind of makes this post absolutely unnecessary lol

[brettcannon]

@XMgzx FYI I made this a Q&A discussion. If you wouldn't mind, could you mark it as answered?