Conda environment revision rollback limits with mixed pip installations

Environment State Recovery

Conda provides a mechanism to revert an environment to a previous state using the --revision flag with the conda install command. This process relies on the local history stored in the environment's metadata to reinstall a specific set of packages.

Mixed Package Manager Constraints

A significant uncertainty exists when environments utilize both conda and pip. While conda tracks its own package changes in the revision log, pip-installed packages are not recorded in this history. Consequently, rolling back to a previous conda revision does not remove or revert packages installed via pip that were added after that revision point.

This behavior creates a potential mismatch between the restored conda package set and the remaining pip-installed dependencies, which may lead to version conflicts or unexpected runtime behavior.

• Does the conda revision system provide any native mechanism to synchronize pip-installed packages during a rollback?
• What is the expected behavior when a conda rollback reinstalls a package that conflicts with a pip-installed package not tracked by the revision history?