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 version in requirements graph for eth-typing #174

Closed
maayank opened this issue Dec 26, 2021 · 4 comments
Closed

Conflicting version in requirements graph for eth-typing #174

maayank opened this issue Dec 26, 2021 · 4 comments

Comments

@maayank
Copy link

maayank commented Dec 26, 2021

Hey @arjanz ,
My project uses pipenv for package management and I get this error when trying to update to the latest substrate-interface:

There are incompatible versions in the resolved dependencies:
  eth-typing<3.0.0,>=2.2.1 (from eth-utils==1.10.0->substrate-interface==1.1.6->-r /tmp/pipenvn7q5cvd_requirements/pipenv-mq4ozh93-constraints.txt (line 12))
  eth-typing<4,>=3.0.0 (from eth-keys==0.4.0->substrate-interface==1.1.6->-r /tmp/pipenvn7q5cvd_requirements/pipenv-mq4ozh93-constraints.txt (line 12))

As you can see, different packages require exclusive version of 'eth-typing' (<3, >=3). What do you suggest?

@arjanz
Copy link
Member

arjanz commented Dec 27, 2021

The conflict is between packages eth-utils and eth-keys, which do not have an overlapping version requirement. What I can try is loosen the version requirement of these two package and hope it resolves.

Interesting is that I don't have this error, are you using the new pip conflict resolution strategy?

@arjanz
Copy link
Member

arjanz commented Dec 27, 2021

I tested several versions of eth_utils and eth-keys and made the version requirement less strict, I think it shouldn't be a problem anymore. You can test by installing Github master if this works for you, then it will be included in next release.

@nsagie8
Copy link

nsagie8 commented Dec 29, 2021

@arjanz
Hi,
I'm working with @maayank
It should be good for us, and we would like you to include it in next release.

Thanks

@maayank
Copy link
Author

maayank commented Jan 4, 2022

Solved with the latest release, thanks @arjanz !

@maayank maayank closed this as completed Jan 4, 2022
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