non-standard module location (again)

Calvin Spealman ironfroggy at gmail.com
Fri Oct 21 12:41:52 EDT 2011


I am biased, but you could use a plugin loader like straight.plugin at
https://github.com/ironfroggy/straight.plugin

On Fri, Oct 21, 2011 at 10:05 AM, Shane <gshanemiller at verizon.net> wrote:
> Need to refine a question I asked earlier. If I have a module,
>
> |--  foo
> |-------|
> |-------|---bar
> |-------|-------|
> |-------|-------|---__init__.py
>
> then I can say import foo.bar
>
> But suppose I want to import foo.bar.stuff and stuff isn't located on
> under `bar' because it's user
> supplied code:
>
> |- stuff                             <- I want this to be logically
> under foo.bar
> |-------|---__init__.py           <- even though it's not under bar in
> the computer's file system
>
> Now what: how to arrange to do command: import foo.bar.stuff
> --
> http://mail.python.org/mailman/listinfo/python-list
>



-- 
Read my blog! I depend on your acceptance of my opinion! I am interesting!
http://techblog.ironfroggy.com/
Follow me if you're into that sort of thing: http://www.twitter.com/ironfroggy



More information about the Python-list mailing list