Fix UnicodeEncodeError by using UTF-8 encoding for migration files (closes #2096) #2097
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.
Description
This PR updates migration file writing to explicitly use UTF-8 encoding instead of ASCII.
Previously, migration files were written with:
This prevented writing non-ASCII characters and could raise:
The implementation now uses:
Motivation and Context
Fixes #2096.
Migration files may contain non-ASCII characters (e.g. verbose names, comments, or field descriptions).
Using a hard-coded ASCII encoding makes such content impossible to write.
UTF-8 is the standard encoding for Python source files and ensures:
This change removes the unnecessary ASCII restriction and improves robustness.
How Has This Been Tested?
Tested locally with:
Steps performed:
tortoise makemigrations.Checklist: