Given the problems experienced with embedding Python, I like the idea of providing these controls.
However, PBS Pro has many (too many?) places for configuration parameters, including:
1. * Command line arguments
2. * Environment variables
3. * Startup scripts (although these usually leverage the above methods)
4. * pbs.conf
5. * Other config files (for MOMs and Schedulers)
6. * qmgr
The design suggests these new config parameters be set via #2, #3, and #4 (only). I'm actually on the fence about this. On the one hand, as experimental parameters, putting them in the least intrusive place possible makes sense. On the other hand, there has been an ongoing desire to make qmgr the single point for configuration. (Qmgr has the advantage of being able to do error checking, perform logging of all changes, and cause new configuration values to actually get used right away. The only thing that can't be in qmgr is how to get to qmgr data -- the networking).
I'd love to see us getting rid of non-qmgr settings rather than adding more.