Skip to content
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

Conflicting versions of stable-baselines and imitation #55

Open
dashpritam opened this issue Jun 14, 2023 · 3 comments
Open

Conflicting versions of stable-baselines and imitation #55

dashpritam opened this issue Jun 14, 2023 · 3 comments

Comments

@dashpritam
Copy link

dashpritam commented Jun 14, 2023

How do I resolve the following conflict? Please help.

I have tried both imitation@tf-master and tf-master-compatibility branch

Linux,
Python 3.7
Tensorflow 1.15

The conflict is caused by:
    evaluating-rewards 0.1.1 depends on stable-baselines 2.10.3a0.-WIP- (from git+https://github.com/hill-a/stable-baselines.git)
    imitation 0.1.1 depends on stable-baselines~=2.10.1

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict
@kierad
Copy link

kierad commented Jul 12, 2023

Hello, I'm also seeing this error when installing this repo.

> python -V
Python 3.7.17
> pip list
Package    Version
---------- -------
pip        23.1.2
setuptools 47.1.0

OS: MacOS Ventura 13.4.1

@sibiraja
Copy link

I also am getting the same issue. I attempted to solve the problem by creating forks of both the evaluating_rewards repo and and stable_baselines repo, and changing the version string in stable-baselines/stable_baselines/version/txt, and setting the dependency in evaluating-rewards/requirements.txt to point to my forked version of stable-baselines. This seems to fix the initial issue that you pointed out. However, I need to downgrade my python version to 3.7 in order to install tensorflow 1.15, but homebrew does not support python 3.7. Not sure if there is a workaround beyond a manual installation of python 3.7

@sibiraja
Copy link

Update, the best workaround seems to be using a Docker container as mentioned by Dr. Gleave here:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants