-
Notifications
You must be signed in to change notification settings - Fork 5
Feature: Add Deprecation Message #103
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
Conversation
Solution: loosen it to accept compatible versions to 0.4.2
Co-authored-by: nesitor <[email protected]>
Co-authored-by: Hugo Herter <[email protected]>
…essage for deprecated classes and types.
The PR introduces a significant change to the Python SDK library for Aleph.im network. The changes involve major modifications in The changes are categorized as BLACK because they involve extensive changes to critical components and require deep understanding of the project architecture, including its dependencies and how it interacts with other systems. Only experienced developers should review this PR, as it involves significant architectural changes. The label 'BLACK' is used sparingly in this case, indicating that this PR requires a high level of expertise and attention to detail. Please note that the categorization may not be 100% accurate due to the complexity of the changes involved. It's always recommended to review the code changes thoroughly before merging them into the main branch. |
Problem: too strict aleph-message dependency Solution: loosen it to accept compatible versions to 0.4.2 Co-authored-by: Hugo Herter <[email protected]>
Deprecation messages are displayed when either trying to use the now abstract classes
AlephClient
andAuthenticatedAlephClient
in the form of eitherImportError
when imported directly fromaleph.sdk
NotImplementedError
when imported from their source files, with additional info about which classes to use instead.