* bukzor <workithar...@gmail.com> [110313 15:48]: > > Thanks Tim. > > I believe I understand it. You create loaders in a flat organization, > in the same directory as your shared library, so that it's found Not in the same directory as shared libraries.
> naturally. These loaders use custom code to find and run the "real" > scripts. This seems to be a combination of solutions d) and e) in my > above post. In my case, the loader 1)Executes code that would otherwise be duplicated. 2)Loads modules (usually from a lower-level directory) based on keywords passed as a URL segment. > > It seems to have few disadvantages, although it does obfuscate where > to find the "real" code somewhat. It also has the implicit requirement > that all of your scripts can be categorized into a few top-level > categories. Correct. In my case that is desirable. > I'll have to think about whether this applies in my > situation... cheers -- Tim tim at johnsons-web.com or akwebsoft.com http://www.akwebsoft.com -- http://mail.python.org/mailman/listinfo/python-list
