Andy,

> I guess the rest of DM will also need for some sort of configuration
> so maybe this issue needs a wider discussion to set on something 
> common? Or is it already decided and YAML is the only option for 
> non-Butler (non-qserv) use?

	As I mentioned, it has already been decided a while ago that:

> > The core LSST stack currently has two choices for configuration:
> > pex_config or YAML.

> Personally I have no direct experience with YAML. After reading all I 
> can find I'm almost OK with YAML, the only thing that bothers me is 
> Python-ish whitespace use for structure.

	We shouldn't let the perfect be the enemy of the good enough.

	And this isn't banning anything else if you find something, it's
just setting a high barrier to adoption:

> > If you'd like to use something other than the above, you'll have to show
> > that those options are insufficient or that your other solution is far
> > superior (not just marginally better).

-- 
Kian-Tat Lim, LSST Data Management, [log in to unmask]

########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1