Loosen eth-abi dependency

[MHHukiewitz]

Problem: Too strict of a eth-abi==4.0.0b2 dependency makes it difficult to install the latest version of the SDK on aleph-nodestatus.

[github-actions]

User Message

--- aleph-im/aleph-sdk-python ---
Python SDK library for the Aleph.im network

Rules: No additional rules provided

Diff:
diff --git a/setup.cfg b/setup.cfg
index de50520..06a88f9 100644
--- a/setup.cfg
+++ b/setup.cfg
@@ -41,7 +41,7 @@ install_requires =
aleph-message~=0.4.3
eth_account>=0.4.0
# Required to fix a dependency issue with parsimonous and Python3.11

• eth_abi==4.0.0b2; python_version>="3.11"

• eth_abi>=4.0.0; python_version>="3.11"
  python-magic

The usage of test_requires is discouraged, see Dependency Management docs

tests_require = pytest; pytest-cov

diff --git a/tests/test_sdk.py b/tests/test_sdk.py
new file mode 100644
index 0000000..e9f5723
--- /dev/null
+++ b/tests/test_sdk.py
@@ -0,0 +1,8 @@
+import pytest
+from aleph_message import Message
+from eth_account import Account
+
+def test_sdk():

• account = Account()
• message = Message(content="Hello, world", sender=account.address)
• assert message.sender == account.address

### Assistant

BLACK: This PR is categorized as 'BLACK'. The changes involve a significant amount of codebase modifications. It includes the upgrade of eth_abi dependency to version 4.0.0 or higher, which could potentially introduce breaking changes if not handled properly. Additionally, it also updates python-magic library, which might require changes in other parts of the system that use this library. The PR description mentions tests_require but no specific test cases are provided. It's recommended to have a deep understanding of the project architecture and thorough testing before merging these changes.

The addition of new file `tests/test_sdk.py` provides some basic unit tests for the SDK, which is good practice for maintaining code quality. However, it would be beneficial if more comprehensive test cases were provided to ensure that all parts of the library are working as expected. 

Please note that this PR might require a deep understanding of the project architecture and thorough testing before merging these changes. The reviewer should consider the potential impact on other parts of the codebase and thoroughly test the changes in a staging environment before approving the PR.

### User Message

--- aleph-im/aleph-sdk-python ---
Python SDK library for the Aleph.im network 

Rules: No additional rules provided

Diff:
diff --git a/setup.cfg b/setup.cfg
index de50520..06a88f9 100644
--- a/setup.cfg
+++ b/setup.cfg
@@ -41,7 +41,7 @@ install_requires =
     aleph-message~=0.4.3
     eth_account>=0.4.0
      # Required to fix a dependency issue with parsimonous and Python3.11
-    eth_abi==4.0.0b2; python_version>="3.11"
+    eth_abi>=4.0.0; python_version>="3.11"
     python-magic
 # The usage of test_requires is discouraged, see `Dependency Management` docs
 # tests_require = pytest; pytest-cov
diff --git a/tests/test_sdk.py b/tests/test_sdk.py
new file mode 100644
index 0000000..e9f5723
--- /dev/null
+++ b/tests/test_sdk.py
@@ -0,0 +1,8 @@
+import pytest
+from aleph_message import Message
+from eth_account import Account
+
+def test_sdk():
+    account = Account()
+    message = Message(content="Hello, world", sender=account.address)
+    assert message.sender == account.address

Assistant

BLUE: This PR is categorized as 'BLUE'. The changes are minor and do not involve significant codebase modifications. It includes the upgrade of eth_abi dependency to version 4.0.0 or higher, which should not introduce any breaking changes if properly handled. Additionally, it updates python-magic library, but this change is unlikely to affect other parts of the system as long as proper compatibility is ensured. The PR description mentions tests_require but no specific test cases are provided. However, adding a new file tests/test_sdk.py provides some basic unit tests for the SDK which could be beneficial in maintaining code quality.

Please note that this PR might require a deep understanding of the project architecture and thorough testing before merging these changes. The reviewer should consider the potential impact on other parts of the codebase and thoroughly test the changes in a staging environment before approving the PR.

[hoh]

Why is the dependency present twice ?

If it is already in install_requires, no need to provide it in [ethereum]