Consider removing config APIs
vyasr opened this issue · 2 comments
Currently signac allows users to interact with the config via both Python APIs and the CLI. While this model makes sense for most of signac, it is generally unnecessary for configs. In fact, changes like glotzerlab/signac-flow#573 are moving us towards completely decoupling the configuration logic and just sharing the file. We should investigate whether this approach is viable for signac-flow/other plugin compatibility (i.e. if packages built on top of signac could just rely on configobj directly), in which case we could remove config APIs entirely from signac.
Based on various recent discussions, we can remove config APIs from signac. signac-flow has been updated accordingly. In the meantime, we need to deprecate all config APIs in preparation for this.