Note that we're highly unlikely to ever accept a PEP to provide this natively, as it couples the process of runtime module loading too tightly to what should be private organisational details of the software publication process (domain names, repository names, etc).

We already know from experience with Java component naming that these kinds of approaches simply don't age well for widely adopted software in a distributed development context, as they turn things that shouldn't have any software compatibility implications (renaming a development repository, moving to a different repository hosting provider, selling a company) into major API compatibility management headaches.

While there are some reasonable applications for the feature when it comes to private software modules that are used only within a single (relatively small) organisation, the existence of httpimport also shows that there aren't any further changes needed to the core import system to enable it.