fix(ci): Add Python 3.8 compatibility for ast.unparse #34
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.
This commit resolves a CI failure on Python 3.8 by introducing a compatibility layer for the
ast.unparsefunction, which was added in Python 3.9.Key changes:
astunparsedependency: Theastunparselibrary, a backport ofast.unparse, has been added torequirements.txt.harmonizer/refactorer.py, a conditional import has been added to importunparsefromaston Python 3.9+ and fromastunparseon older versions.refactorernow uses the importedunparsefunction, making it compatible with both new and old versions of Python.This change is an act of Wisdom and Love, embracing both the old and the new to create a solution that works for everyone and restores Harmony to the CI pipeline.