All commit authors signed the Contributor License Agreement.

Thanks! I was planning to implement this at some point, but you beat me to it :) I haven't checked too deeply, but we should make sure to only autocomplete these submodules when we are sure they are coming from the stdlib. We do not want to autocomplete them when a user intentionally shadows an stdlib module with their own because in that case they might not exist.

but we should make sure to only autocomplete these submodules when we are sure they are coming from the stdlib. We do not want to autocomplete them when a user intentionally shadows an stdlib module with their own because in that case they might not exist.

Yeah, I wondered about that, I'll check if we have a reliable and fast way to check this. Just looking atModuleInfo.file_finder.path to see if it is relative to the stdlib path may do the trick!

A side note on this: when testing the current behavior by creating a foldercollections with__init__.py andfoo.py in it, the current mechanism suggestcollections.foo, but is cannot be imported... becausecollections was already imported at startup (because of interactive mode):

% mkdir collections% touch collections/__init__.py collections/foo.py% pythonPython 3.14.0rc2 [...]>>>from collectionsimport<TAB>>>>from collectionsimport fooTraceback (most recent call last):  File "<python-input-0>", line 1, in <module>    from collections import fooImportError: cannot import name 'foo' from 'collections' (/Users/loic/cpython/Lib/collections/__init__.py)>>>% python -c "from collections import foo; print(foo)"<module 'collections.foo' from '/Users/loic/test/collections/foo.py'>

Not directly related, but it may be cool to check if the name to complete is already insys.modules, and if yes only suggest imports from the location of the imported module.

Thanks@loic-simon for the PR, and@ambv for merging it 🌮🎉.. I'm working now to backport this PR to: 3.14.
🐍🍒⛏🤖

GH-138943 is a backport of this pull request to the3.14 branch.

Not directly related, but it may be cool to check if the name to complete is already insys.modules, and if yes only suggest imports from the location of the imported module.

Adressed in#139461.