Re: Proposal: private keyword for import statements to hide module dependencies

I agree that some of my reasoning was off and it does not directly with the issue of sub-dependencies. 
However, the Idea was more on how to hide it rather than the dependency issue itself. 
Anyways, I agree that an approach on name mangling might be more in line with what we have in python.

How I understand your Idea is that we write the classname like below?
'''
class __Calculator__:
    pass
'''

Would it be possible to do the same with for example imports of code you have no control over. Like below?

'''
import __numpy__ as np
'''