Importing dynamically loaded modules (in packages)?

[holger krekel]

[Steve Holden]
> [Holger Krekel]
> > There is no 'package' object to start with and package
> > functionalities are not encapsulated anywhere.
> > So it seems approriate to think of a package as a
> > concept of nested modules and accessing them with
> > respect to directory structure and filesystem-coupled
> > initialization.
> >
> A package is a directory containing an __init__.py file. 

And that's where it starts to fall out of pythons object world. 
There is no 'directory'-object. 

> When the package is
> imported (which mjust happen before any submodules or subpackages can be
> imported) the __init__.py file is executed. 

The next filesystem-dependence not related to python's object structure.

> > imho Python3 should have a better grip
> > on packages.
> >
> imho Motherhood and apple-pie are good ;-)
> Anything that makes Python applications easier to package and distribute
> will be a good thing. "Python 3 should have a better grip on packages" comes
> nowhere near making Python applications easier to package and distribute ;-)
> > Is their already something underway?

regard my sentences as a careful check to make sure i am not missing
something. Sometimes there are these nice 'has been discussed and
rejected before' or 'GvR said no' or similar landmines.

> a-better-question-is-who's-going-to-do-something-about-it-ly y'rs  - steve

I'd like to come up with a small proposal. Not right now, though :-)
If nobody thinks that this should be left to the gurus, anyway.

another-question-is-if-there-is-a-real-need-besides-my-own-ly yours holger