If pyctdev were to optionally support reading config from setup.cfg, the travis and appveyor files for our various projects could be simplified more. Also, it would make it easier to run tasks locally (no need to supply options, for which the travis file typically is the reference...). Additionally, lots of pyviz projects share the same values for lots of the config, so we could have defaults that allow less per-project config.
However, I'd really like to sort out the command line parameter handling before that (which might involve changes to doit, or wrapping doit, or not using doit; not sure yet)...
If pyctdev were to optionally support reading config from setup.cfg, the travis and appveyor files for our various projects could be simplified more. Also, it would make it easier to run tasks locally (no need to supply options, for which the travis file typically is the reference...). Additionally, lots of pyviz projects share the same values for lots of the config, so we could have defaults that allow less per-project config.
However, I'd really like to sort out the command line parameter handling before that (which might involve changes to doit, or wrapping doit, or not using doit; not sure yet)...