Skip to content

[networkx] Correct argument type for from_nested_tuple #14218

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

Merged
merged 1 commit into from
Jun 10, 2025

Conversation

AckslD
Copy link
Contributor

@AckslD AckslD commented Jun 4, 2025

Currently the type hint specifies a tuple of length one with an arbitrary element. However the tuple passed may be of any length. It is actually an arbitrary nested tuple of tuples but not sure how to annotate that or if it's necessary.

Currently the type hint specifies a tuple of length one with an
arbitrary element. However the tuple passed may be of any length. It is
actually an arbitrary nested tuple of tuples but not sure how to
annotate that or if it's necessary.
Copy link
Contributor

github-actions bot commented Jun 4, 2025

According to mypy_primer, this change has no effect on the checked open source code. 🤖🎉

Copy link
Collaborator

@Avasam Avasam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

For nested tuples: I think you can make a self-referencial type-alias. Something like

_T = TypeVar("_T")
_NestedTuple: TypeAlias = tuple[_NestedTuple | _T, ...]

# Usage:
_NestedTuple[str]

But your current fix is perfectly fine as is. You can explore a more complete annotation in a separate PR.

@Avasam Avasam merged commit 9a92309 into python:main Jun 10, 2025
49 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants