Making PDDF 2.0 base classes python3 compliant #6924
Merged
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.
Why I did it
We need to make the PDDF 2.0 base API implementation python3 compliant
How I did it
How to verify it
Verified it with a sample AS9716 (TH3) platform which is being using PDDF as in PR (#6902).
Without these changes we were not able to load the PAI 2.0 and getting the following errors.
After the fix,
Which release branch to backport (provide reason below if selected)
Description for the changelog
Related to the PR (#6902)
A picture of a cute animal (not mandatory but encouraged)