Skip to content
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

LeapSecondInfo: use dataclass instead of NamedTuple #13

Merged
merged 2 commits into from
Jun 6, 2024

Conversation

jepler
Copy link
Owner

@jepler jepler commented Jun 6, 2024

The documentation workaround for the dataclass was worse than the benefit from being able to tuple-unpack it.

jepler added 2 commits June 5, 2024 21:06
The documentation workaround for the dataclass was worse than the
benefit from being able to tuple-unpack it.
@jepler jepler merged commit ed0ebaa into main Jun 6, 2024
20 checks passed
@jepler jepler deleted the change-leapsecondinfo-type branch June 6, 2024 02:11
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.

1 participant