and therefore I now have conflicting dependencies with eth-typing and eth-utils because eth-ape wants versions <4, <3 respectively, but siwe-py wants versions 4.x.
(Issue #71 )
Resolution
Since the siwe-py library is so light, it was unclear to me the need for such a strict restriction on eth-utils and eth-typing, so I modified the pyproject.toml.
The tests for the library pass and I've tested using the update code as a github dependency and all works well, at least for the nucypher/nucypher library 😊 .
I'm hoping this can be included in a release relatively quickly.
This is starting to get complex and would deserve to run the tests for various versions of eth-account, but I'm going to trust that you tested with the older version for now.
Issue
I'm trying to use the latest
siwe-py
library which has a fix I need in a newer version (>v2.4.1) but has the following dependencies (https://github.com/spruceid/siwe-py/blob/v4.1.0/pyproject.toml):However, I'm also using
eth-ape
for testing, which has the following dependencies:and therefore I now have conflicting dependencies with
eth-typing
andeth-utils
becauseeth-ape
wants versions <4, <3 respectively, butsiwe-py
wants versions 4.x.(Issue #71 )
Resolution
Since the
siwe-py
library is so light, it was unclear to me the need for such a strict restriction oneth-utils
andeth-typing
, so I modified the pyproject.toml.The tests for the library pass and I've tested using the update code as a github dependency and all works well, at least for the
nucypher/nucypher
library 😊 .I'm hoping this can be included in a release relatively quickly.
Fixes #71 .