Issues with .dctaprc as a config file name about dctap-python HOT 4 CLOSED

@nishad Can you suggest an alternative filename?

from dctap-python.

I like to call it just dctap.yaml, since I prefer yaml as the standard extension as per the official recommendation [1]. Our config is structured, so simply calling it dctap will give us more flexibility in future expansions. Another possibility is, making all dctap parsers respect dctap.yaml, not just the Python implementation.

[1] http://yaml.org/faq.html

from dctap-python.

@nishad
dctap.yaml is the default, but I am now implementing a command-line option, --hidden, such that dctap init --hidden writes a new config file to .dctaprc.

The dctap read command, then, would look first for dctap.yaml and, if not found, would then look for .dctaprc. If neither file were found, it just uses some built-in defaults.

Does that seem like a reasonable approach? Or do you think that even this could cause "unexpected side effects"?

from dctap-python.

As described above, this has been addressed.

from dctap-python.