DataSpell Virtual Environment ↔ Docker Container: Synchronizing Python Packages

Integration Goal

Maintain a single source of truth for package versions across a DataSpell project’s local virtual environment and any Docker containers launched from the IDE.

Current Constraints

DataSpell can create a dedicated venv per project but does not auto‑pin or refresh dependencies when changes occur outside the IDE. The Docker tool window can launch containers, but the IDE does not propagate package changes between the container and the local venv. External edits to requirements.txt or environment.yml are only recognized after a manual refresh or IDE restart.

Unresolved Decision

1. Should DataSpell automatically detect and rebuild the local virtual environment when requirements.txt or environment.yml is modified externally?
2. Can Docker containers be configured to mirror the local environment’s package list on startup, and if so, how can this be exposed in the IDE?
3. What observer mechanism could DataSpell integrate to watch for changes in either the local venv or the Docker container and trigger a sync?