[6.x.x] Migrate to new Python generator #4125
Open
Conversation
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
dschwartznyc
changed the title
chrisisla
approved these changes
Oct 28, 2025
|
Superseded by #4141 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Technical Change - Update Python generation to utilize the new process
Background
The upcoming release of CDM 7 will standardize the serialization format (Issue #3236) and include a new Python library generated by updated tooling.
What is being released?
The Python library will use updated tooling that supports metadata. Python support for functions will arrive in a subsequent update.
Note that the new Python library for CDM 6.x will use the new serialization format that is not backward compatible with data produced by the old Python libraries. Before standardization, cross-language data exchange (e.g., between Java and Python) was not guaranteed. The new Python tooling facilitates such compatibility by implementing the new format.
Detail on the changes can be found at Issue #3878