The PipelineTask activator's use of multiprocessing means that exceptions need to be pickleable for us to get decent tracebacks.  The lack of this makes debugging concrete PipelineTasks difficult.

It is currently unclear if this is a problem for all pex.exceptions.Exceptions or just the subclasses in meas_base.