Sounds good to me.. But a couple of questions.  First: would this be useful in resolving some cycle problems, such as when module A depends on module B which depends on module A?  Second, and I think it's been brought up already, what syntax are you looking into?  Aka, would a module declare what modules it wants hidden from its own dependants, or is it the other way around?  Or, better yet, both?  I'm picturing something like this:

    module A;
    import B;              //normal
    import(local) C;    //invisible to dependants
    import(base) D;    //excludes D's dependancies

I'm not recommending the labels 'local' and 'base' neccessarily.. although I do like local, but you get the idea.  And it still wouldn't hurt to allow the module-aliasing and symbol-import ideas that've been brought up earlier, a la 'import A as B;' and 'import A.MyClass;' the latter of which could behave like a 'base' import that's specific to particular component of the module.

 -- C. Sauls