Remove duplicate __all__ declarations in vectorized_mobject.py #4108
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.
Overview: What does this pull request change?
This pull request removes duplicate
__all__
declarations and redundant entries within thevectorized_mobject.py
module. By consolidating the exports list into a single__all__
, this change ensures clarity, avoids confusion, and eliminates unnecessary duplication.Motivation and Explanation: Why and how do your changes improve the library?
Why:
Having multiple
__all__
declarations in the same module is unnecessary and can create ambiguity. Moreover, redundant entries such asVectorizedPoint
within the list serve no functional purpose and can confuse contributors or maintainers.By consolidating
__all__
into a single declaration and removing duplicates, this change aligns with Python's best practices for maintaining clean and readable code.How:
This change:
Merges the two
__all__
declarations into a single list at the top of the module.Removes duplicate entries such as
VectorizedPoint
from the export list.Ensures the final
__all__
is clear, concise, and reflective of intended exports.Links to added or changed documentation pages
Further Information and Comments
This is a non-breaking, backward-compatible change. It does not modify exported functionality but improves the codebase's maintainability by ensuring consistency and reducing redundancy.
Feedback or further suggestions are welcome!
Reviewer Checklist