Clarify deprecated channel properties will be removed in v0.6.0 - #196
Merged
Conversation
Update all deprecation messages, docstrings, and documentation to specify v0.6.0 as the removal version for channel-level port properties (opx_output_offset, filter_fir_taps, filter_iir_taps, shareable, inverted, rf_frequency, and related I/Q/input variants).
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.
Summary
channels.pyto say "will be removed in v0.6.0" instead of "in a future version"rf_frequencydeprecation warning to include the v0.6.0 removal noticedocs/components/channels.mdanddocs/components/channel-ports.mdto reference v0.6.0 throughoutCHANGELOG.mddeprecated entries to explicitly state v0.6.0 removalBackground
Deprecated properties (
opx_output_offset,filter_fir_taps,filter_iir_taps,shareable,inverted,rf_frequency, and their I/Q/input variants) were introduced and deprecated within the same v0.5.0 alpha cycle (PR #172). Users on stable v0.5.0 deserves a clear deprecation period before removal. This PR sets the removal target to v0.6.0.Related: PR #195 contains the actual removal (to be merged after v0.6.0 is tagged).
Test plan
627 passed)