Hi. I am taking a look a supervisor so will likely have a couple of questions over the next few days. First, thank you for making this available.
I interested in whether there can be a more cooperative options parsing scenario with integration of supervisor within a buildout. Perhaps this could mean letting buildout handle the collection of configuration data so as not to rely upon a .conf file at one of three possible hard coded locations in options.py or passing a file to the startup script. I would prefer for it to be read and parsed as part of the buildout wherever it happens to be. Obviously the scripts need to be aware of this location as well in this scenario. Also, I do not use ez_install and tend not to rely on the system python at all. Generally, it can be the source of inconsistency and frustration between platforms and transitions from development to deployment. In my buildout, supervisor pulls in ez_install. setuptools being already available to my project and ez_install is not used. Many thanks. Regards David _______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
