On Thursday, 9 June 2011 16:22:10 UTC+2, Anthony wrote: > > But in a web2py app, you would have something like > /applications/Cast/modules/cast.py, and in your code you would just do > 'import cast'. My understanding of the problem is that in that case, the new > web2py importer tries to import applications.cast.modules.cast instead of > applications.Cast.modules.cast, which results in an import error. >
Yes, this is a good point. I shall take a gander at Pierre's custom_import.py if I get some time later. I didn't realise the import path chain was being generated by web2py. That makes it our responsibility to fix.
