New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
obs_test Tickets/dm 8686 #27
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks OK
_policy: !!python/object:lsst.daf.persistence.policy.Policy | ||
data: | ||
exposures: | ||
raw: {template: raw/v%(visit)d_f%(filter)s.fits.gz} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We do not extend our 4-space indent policy to YAML files?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't even think about it. 2 spaces seems to be the default for yaml.dump
. I can specify the indentation level when I call dump
though.
@timj is 2 spaces ok or should I specify 4?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm happy with 2, especially if that is the default for YAML serialization.
Remove use of older, unpublished _policy.paf/yaml mechanism. Rewrite test to use the RepositoryCfg in-repo policy. Rewrite the test to *not* use in-repo policy from parents, which is how it is described in LDM-463. is what is stated in LDM-
and pass them to the superclass
768cf5b
to
1327e5c
Compare
No description provided.