You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that a namer bug in 1.0.0, fixed in 1.0.1, is still (or differently) broken when executing under conda run python -m nose. I've had to pin approvaltests back to 0.8.0 to get working test execution.
When executed under my environment separately, approval test output files appear in the expected location.
conda activate my_env
python -m nose
But when executed under a default no-environment shell, the approval test output files appear next to the nose module from my environment.
conda run -n my_env python -m nose
The text was updated successfully, but these errors were encountered:
bryceschober
changed the title
Namer still broken under conda run
Namer still broken under conda run python -m noseJul 21, 2021
It appears that a namer bug in 1.0.0, fixed in 1.0.1, is still (or differently) broken when executing under
conda run python -m nose
. I've had to pin approvaltests back to 0.8.0 to get working test execution.When executed under my environment separately, approval test output files appear in the expected location.
But when executed under a default no-environment shell, the approval test output files appear next to the nose module from my environment.
The text was updated successfully, but these errors were encountered: