Currently, ReplayPythonUsage assumes outputs that weren't included in the Replayed artifacts' provenance are not of interest. They are templated out as _ variables, so cannot generally be interrogated or saved to disk. This behavior is inconsistent with ReplayCLIUsage, because of the different requirements of those two interfaces, but we should allow users to replay all results via the Python3 API.
Currently, ReplayPythonUsage assumes outputs that weren't included in the Replayed artifacts' provenance are not of interest. They are templated out as
_variables, so cannot generally be interrogated or saved to disk. This behavior is inconsistent with ReplayCLIUsage, because of the different requirements of those two interfaces, but we should allow users to replay all results via the Python3 API.