Problem
Currently each compute instance can only be associated with one requirements.txt file. This limits flexibility for users working across multiple projects that require different dependencies. Switching between projects / tasks still requires manual editing of requirements.txt and file replacement (uninstall / install).
Proposed resolution
- Allow multiple
requirements.txt files to be registered per compute, with an option to select one when starting or switching projects. - Optionally support project-level dependency files for automatic environment setup.
Benefits
- Flexibility: Easily manage and switch between dependencies for different projects.
- Efficiency: Reduce manual configuration time and errors.
- Scalability: Simplify collaboration across teams with diverse workloads.
