Repository navigation
Conversation
The >=3.11 came from the initial commit and was never earned: dcio uses no 3.11 syntax and no 3.11 stdlib -- no tomllib, no typing.Self, no exception groups, nothing. It became a real constraint when SCALCS took dcio as a dependency. SCALCS supports 3.10, so pip could not resolve the requirement there at all, and its linux-py310 job failed outright. The alternatives were to drop 3.10 from SCALCS to satisfy a floor that was not required, or to keep two copies of burst segmentation. Neither is worth it. CI now covers 3.10 through 3.13, and the oldest-deps job pins 3.10 as well, so the floor is a tested fact rather than an assertion -- which is the same reason that job exists for numpy. EKDIST's >=3.11 was inherited from this one and can come down too. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or 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
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.
The
>=3.11came from the initial commit and was never earned: dcio usesno 3.11 syntax and no 3.11 stdlib — no
tomllib, notyping.Self, noexception groups, no match statements, nothing.
It became a real constraint when SCALCS took dcio as a dependency
(DCPROGS/SCALCS#18). SCALCS supports 3.10, so pip could not resolve the
requirement there at all:
The alternatives were to drop 3.10 from SCALCS to satisfy a floor that is not
required, or to keep two copies of burst segmentation in the stack. Neither is
worth it.
Proven, not asserted
CI now covers 3.10 through 3.13, and the
oldest-depsjob pins 3.10 aswell — so the floor is a tested fact, for the same reason that job already
exists for the numpy minimum.
345 passing.
EKDIST's
>=3.11was inherited from this one and can come down too, in itsown change.
Merge and I will tag
v0.1.1.🤖 Generated with Claude Code