-
-
Notifications
You must be signed in to change notification settings - Fork 34k
bpo-39206: Add encoding detecting to modulefinder #17817
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA). CLA MissingOur records indicate the following people have not signed the CLA: For legal reasons we need all the people listed to sign the CLA before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. If you have recently signed the CLA, please wait at least one business day You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
|
Just recording, I just signed the CLA. |
a47ad67 to
8251bd0
Compare
8251bd0 to
0c465a0
Compare
|
Could you also add some more tests for this issue? |
Thanks, will do it!
Of course! I will add some tests to |
|
It might be at least worth setting up tests to open files with odd encodings. Test it on a file with some Unicode characters in it, and on files with PEP263 style encoding declarations. On a different note, I would point out that when running files, they are opened in bytes mode and that's it. Encoding is inferred during the compilation process, simply by running the compile() function on the bytestring read from the file, with no need to import tokenize or open in 'r' mode or anything else. |
|
@plokmijnuhby I've added one example, could you please give me feedback on it? If it's ok, I will add one ow two more with different encoding types or testing default is type to |
Misc/NEWS.d/next/Library/2020-01-06-22-39-23.bpo-39206.zKSTwb.rst
Outdated
Show resolved
Hide resolved
|
Hey guys, just to say that I have been away for a few days but I'll come back to this tomorrow. Sorry for my absence! |
2b33a8a to
c8c81e4
Compare
c8c81e4 to
6ede14d
Compare
e1613f8 to
2b594a9
Compare
asottile
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
otherwise looks great -- thanks for sticking with this!
|
@asottile all checks pass now, do I need to add anything else? Also, I don't know why my PR is still as CLA not signed, but I've already signed it and also registered at |
|
the CLA thing is weird, the app says it isn't linked to your github user -- did you maybe sign it with a different email / account? |
I certainly did with the same e-mail, I'll check if I can link these things! |
|
@asottile I'm all set now! What's the next step? Thanks for your support! |
|
now we wait! this is the unfortunate part about committing to cpython -- there are very few core devs which can merge a PR this looks good though :) |
@asottile thanks! should I squash the changes into one commit while we wait? |
|
iirc it doesn't matter, commits will get squashed upon merge |
c59443f to
0adc639
Compare
|
Just registering here that I accidentally added a commit with |
|
Seems similar changes was already made in #19488. |
Fixing issue 39206.
https://bugs.python.org/issue39206