On Mon, 2003-06-30 at 18:57, Randall Randall wrote: > > I found a similar problem had by Edmund Lian on the Cheetah list, > > but the cause there (class name not being the same as the filename) > > doesn't seem to apply. > > > > Anyone know why this could be happening? > > Well, evidently no one did. > > So, having finally got to the "deploy on Linux" stage, I find > that this error doesn't happen on Linux, but only Mac OS X (my > development platform), which makes me very happy. :) > > So, if anyone needs additional information and wants to try to > track this down in Webware 0.8, I'd be happy to give you more > info, but don't know what would be useful. Eventually I'll try > to do that myself, but it may be some time before I'm able to > take the time.
Sorry, I thought someone else might pipe up about it. Anyway, this was at one point commonly caused by path problems (sys.path), where a module can be imported more than once. Imagine a path like: ['/path/to/Webware', '.'] Where the current directory is /path/to/Webware/WebKit Then you can import Servlet as: from WebKit.Servlet import Servlet or: from Servlet import Servlet Python doesn't recognize that these are the same module, so there are two classes going by the same name. You might look at the class's __module__ attribute to find out more. It might depend on the way you are running the AppServer, environmental variables, etc., which would explain why it works in one environment and not another. Ian ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
