internal/project/detector.go maps file patterns to stores, but it only looks for requirements.txt, pyproject.toml, and Pipfile when deciding the Python/data-science stack. Projects that rely on environment.yml (Conda) or conda.yml lose out on automatic detection and do not get the cue store install data-science recommendation.
Could we add detection signals for environment.yml, conda.yml, and even .envrc files so that the StoreName can point to data-science (or another store) when these files are present? That would cover the common Conda/science workflows that the current detector silently ignores.
internal/project/detector.gomaps file patterns to stores, but it only looks forrequirements.txt,pyproject.toml, andPipfilewhen deciding the Python/data-science stack. Projects that rely onenvironment.yml(Conda) orconda.ymllose out on automatic detection and do not get thecue store install data-sciencerecommendation.Could we add detection signals for
environment.yml,conda.yml, and even.envrcfiles so that theStoreNamecan point todata-science(or another store) when these files are present? That would cover the common Conda/science workflows that the current detector silently ignores.