fix: solve mypy errors which are due to same object names in core.py and channels.py #3414
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.
Fixes #3408. See this comment for a description of the issue). This PR adds
__all__
tocore.py
which includes all objects which were previously exported except forColor
andText
which are names which are also defined inchannels.py
. With this, mypy can correctly detect the type of the top-levelaltair.Color
andaltair.Text
as coming fromchannels.py
and notcore.py
.I've tested against the main branch that all objects are still exported except for some objects from
typing
which are not needed anyway. On the top-level of Altair, you can also see that nothing changed as the auto-generated_all__
inaltair/__init__.py
did not change. Hence, this is purely a fix for mypy and does not have any functional implications for users.