-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Closed
Description
Bug Report
dvc pull: ModuleNotFoundError: No module named 'funcy.py3'
Description
When running dvc pull, I get the ModuleNotFoundError: No module named 'funcy.py3' error. Or running any command, really.
This is because dvc has unpinned dep on funcy and funcy went from 1.18 to 2.0 yesterday, apparently with breaking changes.
Traceback (most recent call last):
File "/fsx_home/homes/srdecny/meaning-cuda-11-8/betaenv/lib/python3.10/site-packages/dvc/cli/__init__.py", line 209, in main
cmd = args.func(args)
File "/fsx_home/homes/srdecny/meaning-cuda-11-8/betaenv/lib/python3.10/site-packages/dvc/cli/command.py", line 16, in __init__
from dvc.repo import Repo
File "/fsx_home/homes/srdecny/meaning-cuda-11-8/betaenv/lib/python3.10/site-packages/dvc/repo/__init__.py", line 72, in <module>
class Repo:
File "/fsx_home/homes/srdecny/meaning-cuda-11-8/betaenv/lib/python3.10/site-packages/dvc/repo/__init__.py", line 96, in Repo
from dvc.repo.status import status # type: ignore[misc]
File "/fsx_home/homes/srdecny/meaning-cuda-11-8/betaenv/lib/python3.10/site-packages/dvc/repo/status.py", line 4, in <module>
from funcy.py3 import cat
ModuleNotFoundError: No module named 'funcy.py3'
Reproduce
pip install dvc
dvc pull
Expected
DVC should not crash like that.
Environment information
Output of dvc doctor:
$ dvc doctor
also crashes :)Additional Information (if any):
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels