From: Chuck E. <ec...@mi...> - 2000-12-06 16:32:59
|
At 02:47 PM 12/6/2000 +0100, Mgr. Vladimir Kralik wrote: >Chuck Esterbrook wrote: > > *** Rejected: > > > > [R] The patch eliminates augmenting sys.path with '..' when a module can't > > be located, but I like this. It means that Webware can reside anywhere > > (doesn't have to be in PYTHONPATH) and still work out of the box. That cuts > > one more step out of set up, and the change only occurs when needed. >I prefer make module a python-package, and set it in PYTHONPATH. >How can I derive my own classes ( Application, Session, Page, Servlet >... ) >when Webware(WebKit), isn't in PYTHONPATH ? Consider this code in WebKit: try: import MiscUtils except ImportError: sys.path.append('..') import MiscUtils Now the path containing all the various Webware components (MiscUtils, WebUtils, etc.) is in the Python path. This is merely a runtime fix at start up WebKit finds that it's not in the python path already. This does not change any other code: from WebUtils.WebFuncs import * -Chuck |