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
Added preliminary support for using dvc with a mercurial repository
instead of a git one. Changes include:
- Added a new Mercurial class in scm.py that implements the Base class
- Added python-hglib as a dependency, comparable to gitpython
- Changed various logging messages to reflect multi-vcs support, and
in some cases brought this reporting under the purview of the
particular scm subclass
Note that in rare cases where both a mercurial and git repo are
found in the same repo, a current limitation implies it will always
choose to use git.
This commit includes a shake at supporting installing mercurial
post-update hooks, but they are not well covered the test suite
and will likely need further work. Mercurial handles hooks all
from one file, so it requires additional intelligence to check
whether the hook is already installed.
Fixes # iterative#945
We haven't come back to working on this and now considering the news https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket , it looks like we shouldn't support hg at all, as the demand will most likely be declining from now on. Hg users still can use dvc in --no-scm(see dvc init) mode, which provides all the core features like add/run/repro/push/pull/fetch/status/etc, but without scm tags/branches support for metrics/gc and other operations. Closing.
Need to simply add a proper driver to https://github.com/iterative/dvc/blob/master/dvc/scm.py (see Git class as an example).
The text was updated successfully, but these errors were encountered: