On Fri, Feb 1, 2013 at 2:21 AM, Aarni Koskela <[email protected]> wrote: > Neat! > > You might also want to look at _options/optdefs.py in the uwsgi-docs repo :) > Might be easier to generate stuff from it. I should only figure out a way to > make sure it's in sync with the various option definitions in the actual > plugins, etc (not to mention finish up with the few unported docs pages)...
ha, thanks :) i am intermittently working on a config module that generates JSON configs and it turns out i've already implemented like 90% ... if only i can haz all the code before i [re]write the code. the bits i've done are for work and rather one-off-ish, but what problems are there with plugin options? i just more-or-less recursive grep + a mountain of regex/sed transforms into a raw, but sytactically correct, python file... seems to work fine for plugins. the goal is to use this to detect plugin changes/additions/etc, in addition to the actual object/function being modified, and *how* its modified (eg * or &) so i can filter dupes, and build/derive an internal representation of how each option will affect uWSGI state. this looks pretty cool though, thanks for pointing out; if add/improve it i will certainly make it known. -- C Anthony _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
