You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the tool will find any path containing a .dvc folder, however there are times when it is necessary to initialize dvc in a subdirectory. This comes up when e.g. packaging the mydata.csv.dvc files via, say, importlib to let users treat datasets as dependencies in the code itself.
On that note, dvc actually does this for you, with dvc.api.Repo.find_root(). It may be worth modularizing the assumptions here a bit, to let users assemble the "right" assumptions for what a "root directory" is, while providing sane defaults to the rest.
The text was updated successfully, but these errors were encountered:
The dev branch exposes the underlying functions that allows you to specify the search criteria. https://github.com/chendaniely/pyprojroot/tree/dev. Also the default criteria looks for a directory called ".dvc" exactly, rather than just something that matches the glob ".dvc". Hopefully, this will be released.
However, if dvc does exactly what you need already, then I would just use that.
Currently the tool will find any path containing a
.dvc
folder, however there are times when it is necessary to initialize dvc in a subdirectory. This comes up when e.g. packaging themydata.csv.dvc
files via, say,importlib
to let users treat datasets as dependencies in the code itself.On that note, dvc actually does this for you, with
dvc.api.Repo.find_root()
. It may be worth modularizing the assumptions here a bit, to let users assemble the "right" assumptions for what a "root directory" is, while providing sane defaults to the rest.The text was updated successfully, but these errors were encountered: