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
I searched open reports and couldn't find a duplicate
What happened?
This issue came up in #133. There is an upstream conda test tests/test_create.py::IntegrationTests::test_conda_pip_interop_conda_editable_package which fails.
# should raise an errorwithpytest.raises(PackagesNotFoundError):
# TODO: This raises PackagesNotFoundError, but the error should really explain# that we can't install urllib3 because it's already installed and# unmanageable. The error should suggest trying to use pip to uninstall it.stdout, stderr, _=run_command(Commands.INSTALL, prefix, "urllib3=1.20", "--dry-run")
The expect conda behaviour here assuming pip interop which is not an officially supported feature is to remove the urllib3=1.20 spec from being requested by the user since it is controlled by pip. Correctly an error is being thrown but it is not the one that conda expects. It looks as though libmamba-solver does attempt to recommend updating the pip version using conda-forge but conda catches this as an error after the final solve. See https://github.com/conda/conda/blob/main/conda/core/solve.py#L175-L184. Leaving this detailed issue so that in the future if pip interop is more explored we have a good starting point.
The text was updated successfully, but these errors were encountered:
Checklist
What happened?
This issue came up in #133. There is an upstream conda test
tests/test_create.py::IntegrationTests::test_conda_pip_interop_conda_editable_package
which fails.This issue can be reproduced via
Then running
Getting the following error
Detailed logs here
Diving into the exact test which fails here
The expect conda behaviour here assuming
pip interop
which is not an officially supported feature is to remove the urllib3=1.20 spec from being requested by the user since it is controlled by pip. Correctly an error is being thrown but it is not the one that conda expects. It looks as though libmamba-solver does attempt to recommend updating the pip version using conda-forge but conda catches this as an error after the final solve. See https://github.com/conda/conda/blob/main/conda/core/solve.py#L175-L184. Leaving this detailed issue so that in the future if pip interop is more explored we have a good starting point.The text was updated successfully, but these errors were encountered: