-
-
Notifications
You must be signed in to change notification settings - Fork 29.2k
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
Possible mojibake in pwd.getpwnam and grp.getgrnam #78785
Comments
Wouldn't be better to use %R? The name can contain invisible characters or trailing whitespaces, in which case the traceback can look confusing. Since names are likely created with PyUnicode_DecodeFSDefault(), they can contain undecodable bytes represented as surrogates U+D8XX if the current filesystem encoding doesn't match the filesystem encoding used for creating entries. |
%R sounds like a good idea, but I suggest to only use %R in the master branch. |
What is the policy to amend a new commit to master for %R? Create a new PR? Wont that cause problem with NEWS entry? |
The bug has been fixed. For %R, does someone want to propose a change for master? William? |
I can do it if you feel the need. |
Sure, reuse the same bpo number. You can modify the NEWS entry that you added ;-) |
pwd.getpwnam
andgrp.getgrnam
#9098Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: