Comment 8 for bug 1162031

Both of those alternatives are totally reasonable... but at least IMO they don't feel super great.

For many larger packages (e.g. numpy) an "import numpy as np" style is extremely common, but you still need to import various submodules. If you apply the pattern above, you end up with "import numpy.modulea as np_modulea", "import numpy.random.moduleb as np_random_moduleb", etc. That obviously *works* but ends up creating two independent styles of usage. Not to mention the repetitive boilerplate in the actual imports.

Ultimately it feels like working around an implementation limitation on the linter side. Fine if that's what it takes, better if it's unnecessary!