-
-
Notifications
You must be signed in to change notification settings - Fork 285
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Current breakage of install due to not specifying dm_control version (or versions for any dependency) #125
Comments
I made a pull request which verions dm_control to a specific hash: #126 But:
|
Ah, now I see that they changed the website: https://mujoco.org/download |
had same issue but adding 210 just caused me this issue in Edit: as a temporary workaround, setting |
Can I ask why d4rl is depending on dm_control via git rather than PyPI? |
I decided to change this comment. I am a bit frustrated; but it is what it is and i knew it was not a good idea to create a dependency (even just fro an experimental test for CQL-SAC) on a github repo vs. at least a published .whl. But it is also a pain to maintain stuff so I totally understand, although being transparent in the README.md seems like a small courtesy I personally would do to set some expectations. |
I also just want to add an extra piece of info here. Installing dm_control from git can produce weird error messages on a fresh virtual environment due to some build-time dependencies not being met. I created a PR on the dm-control side to silence this. google-deepmind/dm_control#215. |
Hi folks, a few days ago, this worked, given a working underneath mujoco install:
Although this repo's master branch hasn't been updated since July, the underlying dm_control dependency version is not specified, and it has since updated to mujoco 2.1: google-deepmind/dm_control@420e237
(which doesn't exist publicly yet: https://www.roboti.us/download.html)
This causes the following error when trying to run install d4rl:
Could someone add versions to all dependencies here? https://github.com/rail-berkeley/d4rl/blob/master/setup.py
Also, to clarify: although one could wait until mujoco 2.1 is available, it still seems that versioning the benchmark is required, or some other mechanism for not ensuring regressions?
The text was updated successfully, but these errors were encountered: