Why did we rename PipelineConfigError ?

[tristpinsm]

commit 8f22399 replaced PipelineConfigError with CaputConfigError. There are at least a few instances of this exception being used outside of caput (it is public after all), which are now broken.

e.g.

$grep -r PipelineConfigError draco
draco/core/io.py:                raise pipeline.PipelineConfigError(
grep: draco/core/io.pyc: binary file matches
grep: draco/core/task.pyc: binary file matches
draco/core/task.py:            raise pipeline.PipelineConfigError(msg)

also in the beam code in ch_pipeline (which is where I noticed this)

[jrs65]

I think the ones in draco are changed in a corresponding PR that should have been merged by now. I'm not sure ch_pipeline was checked though. @nritsche maybe add an alias in caput for PipelineConfigError = CaputConfigError, or add it back in but make it deprecated?

[tristpinsm]

I pulled the latest version of master on draco (radiocosmology/draco@43914e3) before checking.

[jrs65]

Oh oops. I guess Rick didn't catch everything. What was the rationale for the rename in the first place?

[nritsche]

Oh oops. I guess Rick didn't catch everything. What was the rationale for the rename in the first place?

...adding config file line numbers to the error output, I think