21 May
1999
21 May
'99
6:55 a.m.
The problem here is that the package's __path__ is not being created this way now; if anyone has time to work on a patch for Python/import.c, I'd be glad to help test it! ;-)
I take care of this in my extension module. If I have a platform dependent implementation of a module I:
try: import extension Fail: use common
I don't think this is the case that's causing problem. The problem is when a submodule on a package is *always* platform dependent (because, for example, it interfaces to another library). -Perry