Part 5 for refactoring bittensor/subtensor.py #1934
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
thewhaleking
requested changes
May 24, 2024
…-5' into refactoring/roman/subtensor-part-5
ibraheem-opentensor
approved these changes
May 24, 2024
thewhaleking
approved these changes
May 24, 2024
3 tasks
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since the refactoring of this module would turn into a large project, it was decided to divide it into several stages.
This is part 5: current part affects everything in this document except of renaming class
subtensoraccording to the CamelCase rule.Test coverage improved.
Part 1 #1911
Part 2 #1913
Part 3 #1923
Part 4 #1931