Fix profiling scripts with a UTF-8 BOM - #1092
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #1091.
Scalene reads the entry script as text, so a leading UTF-8 BOM reaches
compile()and raises aSyntaxError. Useutf-8-sigto consume the BOM while preserving ordinary UTF-8 decoding.Add real CLI regressions for scripts with a BOM, plain UTF-8, and non-ASCII UTF-8 content.
Validation on Python 3.12:
mypy scaleneandruff check scalenepass.