chore(bindings): move the Python bindings onto the 9.0.0 wave - #818
Merged
Merged
Conversation
Held back deliberately until the wave was live, since both consume from the registry rather than by path. - bindings/python: dvb-si and dvb-t2mi 8 -> 9. Builds clean with no code change. - bindings/transmux-py: transmux 0.15 -> 0.20, and its own broadcast-common 8 -> 9. The broadcast-common pin was the interesting one: `Parse` was already imported, but pinning 8 while transmux 0.20 implements the 9.x trait meant `AudioSpecificConfig::parse` resolved against the wrong trait and was reported as not found -- the same two-versions-in-one-graph shape that broke the first v9.0.0 publish run. - Five minors of transmux drift needed two accessor updates: 0.20 moved the sync flag onto `SampleFlags` and made the composition offset a derived accessor computed from pts/dts rather than a stored field. Both crates `cargo check` clean. Neither is a workspace member (each has its own MSRV and PyPI lane), so they are not covered by the workspace gates.
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
1 participant
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.
Post-publish follow-up, held deliberately until the wave was live since both bindings consume from the registry rather than by path.
bindings/python:dvb-sianddvb-t2mi8→9. Builds clean with no code change.bindings/transmux-py:transmux0.15→0.20, plus its ownbroadcast-common8→9.The broadcast-common pin was the interesting part.
use broadcast_common::Parsewas already imported, but pinning 8 while transmux 0.20 implements the 9.x trait meantAudioSpecificConfig::parseresolved against the wrong trait and was reported as "not found" — the same two-versions-in-one-graph shape that broke the first v9.0.0 publish run on dvb-si. Worth recognising on sight: a "method not found" on a type that plainly has it usually means two versions of the defining trait are in the graph, not a missing import.Five minors of transmux drift also needed two accessor updates: 0.20 moved the sync flag onto
SampleFlags, and made the composition offset a derived accessor computed from pts/dts rather than a stored field.Both crates
cargo checkclean. Neither is a workspace member — each has its own MSRV and PyPI lane — so they are not covered by the workspace gates and had to be checked directly.🤖 Generated with Claude Code
https://claude.ai/code/session_01W1HSZPAJUzGhu8BKkqemmX