-
-
Notifications
You must be signed in to change notification settings - Fork 20
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
Unicode assumption fails #4
Comments
Original comment by Klaus Alexander Seistrup (Bitbucket: kseistrup, GitHub: kseistrup). Possible fix
|
Original comment by Anonymous. I am running into this bug also, please fix it. |
jaraco
pushed a commit
that referenced
this issue
Jan 29, 2019
use spaces, fixed indentation, format using autopep8
jaraco
added a commit
that referenced
this issue
Jul 8, 2023
* Create SECURITY.md Signed-off-by: Joyce <[email protected]> * Remove the security contact from the README, as it's now redundant. Closes jaraco/tidelift#3. --------- Signed-off-by: Joyce <[email protected]> Co-authored-by: Joyce <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Original report by Klaus Alexander Seistrup (Bitbucket: kseistrup, GitHub: kseistrup).
Standing in a directory with a setup.cfg file, using python2.7:
So if there accidentally is a file byt the name of s, e, t, u, p, c, f, or g, that file will be read:
Hint: ConfigParser()'s .read() method says that the filename should only be included in the file list if the name is a unicode instance, and thus a plain string object gets treated as a list.
The text was updated successfully, but these errors were encountered: