> My plan is still to accomplish this with Webware.pth. Having the > Webware packages sit next to each other *is key*. It allows > programs like WebKit's Launch.py and MiddleKit's Generate.py to > ensure that the MiscUtils and other packages they use come from > their own Webware package and not from some other location.
A user copy of Webware in PYTHONPATH will automatically override the system-wide 'site-packages' library. What do Launch.py and Generate.py do that requires anything outside of the standard PYTHONPATH behaviour? Are you talking about situations where you have multiple 'instances' of Webware or multiple 'versions' of it? With system-wide distutils installs, multiple instances will all be using the same codebase for things like MiscUtils so there's no issue there. It shouldn't be a problem with multiple versions either. As for your point about an internally developed component becoming an externally developed one and vice versa, that makes sense. The issue then becomes how to make the names more webware-specific for things like MiscUtils, or even UserKit as you just pointed out. It's the ambiguity of the names I don't like. _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
