hi, > That allows people to create their own plugins in separate packages, > and use them by tweaking the configuration > file. The only think that entry point provided here is an automatic > registration at installation time of the "rss" plugins, > so my Atomisatior application can discover then load it at run time. > > So in your way of seeing thing, you'd rather see this registration > mechanism at the application level, > but the you need to provide specific installation instructions for > people that want to add plugins. > e.g. "put your package in this /plugins directory" for example.
wouldn't this be tackled by providing a plugin-discoverer plugin ? kind of like the new import hooks of pep-302 [1] where you have module finders separated from module loaders, or like this library I have been using in my field [2] cheers, sebastien. [1] http://www.python.org/dev/peps/pep-0302/ [2] http://cdsweb.cern.ch/record/865639?ln=pl http://wlav.web.cern.ch/wlav/pybus/index.html http://seal.cvs.cern.ch:80/cgi-bin/seal.cgi/seal/Scripting/PyBus -- ######################################### # Dr. Sebastien Binet # Laboratoire de l'Accelerateur Lineaire # Universite Paris-Sud XI # Batiment 200 # 91898 Orsay ######################################### _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
