[issue36911] ast.parse outputs ast.Strs which do not differentiate between the ASCII codepoint 12 (literal new line) and the ASCII codepoints 134 and 156 ("\n")

2019-05-14 Thread Amber Brown
Amber Brown added the comment: There's a difference between round-tripping back to the source text and correctly representing the text in the source, though. Since I'm using this module to perform static analysis of a Python module to retrieve class/function definitions and their docstrings

[issue36911] ast.parse outputs ast.Strs which do not differentiate between the ASCII codepoint 12 (literal new line) and the ASCII codepoints 134 and 156 ("\n")

2019-05-13 Thread Amber Brown
New submission from Amber Brown : reproducing case: file.py: ``` """ Hello \n blah. """ ``` And then in a REPL (2.7 or 3+): ``` >>> import ast >>> f = ast.parse(open("test.py", 'rb').read()) >>> f <_ast.Module objec

[issue33497] cgi.parse_multipart does not have an associated "errors" parameter with its "encoding" parameter

2018-05-15 Thread Amber Brown
Amber Brown <hawk...@atleastfornow.net> added the comment: This change mirrors the default in FieldStorage (which it calls). If it's not the best option, then it would need to be changed in FieldStorage too. (personally, I don't like strict because UnicodeDecodeErrors on untrusted user

[issue33509] warnings.warn_explicit with module_globals=True raises a SystemError

2018-05-14 Thread Amber Brown
New submission from Amber Brown <hawk...@atleastfornow.net>: Reproducible with: import warnings warnings.warn_explicit("msg", DeprecationWarning, "name", 1, module_globals=None) -- components: Interpreter Core messages: 316578 nosy: hawkowl priority: norm

[issue33497] cgi.parse_multipart does not have an associated "errors" parameter with its "encoding" parameter

2018-05-14 Thread Amber Brown
Change by Amber Brown <hawk...@atleastfornow.net>: -- keywords: +patch pull_requests: +6489 stage: -> patch review ___ Python tracker <rep...@bugs.python.org> <https://bugs.pyt

[issue33497] cgi.parse_multipart does not have an associated "errors" parameter with its "encoding" parameter

2018-05-14 Thread Amber Brown
New submission from Amber Brown <hawk...@atleastfornow.net>: Lack of this parameter means that you may get an exception (if the incoming data is an invalid encoding) you can not get around. This causes Twisted to be unable to provide a compatible API on Python 3.7. -- messages:

[issue31742] Default to emitting FutureWarning for provisional APIs

2017-10-11 Thread Amber Brown
Amber Brown <hawk...@atleastfornow.net> added the comment: > * asyncio & pathlib are already non-provisional, so wouldn't be affected. I was reading this and actually said "wait what I didn't know pathlib was provisional", and went back to check. The warning for it w

[issue31742] Default to emitting FutureWarning for provisional APIs

2017-10-10 Thread Amber Brown
Amber Brown <hawk...@atleastfornow.net> added the comment: > What happened to "consenting adults"? Consent does not mean that by using Python, users fully consent to using modules that they may not be aware will, to paraphrase Donald, come back to bite them in the ass

[issue31742] Default to emitting FutureWarning for provisional APIs

2017-10-10 Thread Amber Brown
Amber Brown <hawk...@atleastfornow.net> added the comment: So you're proposing a coordinated effort across the half dozen, possibly more, test runners to enable some flags, so CPython doesn't log a single message, possibly two, that you're using unsupported experimental so

[issue31742] Default to emitting FutureWarning for provisional APIs

2017-10-10 Thread Amber Brown
Amber Brown <hawk...@atleastfornow.net> added the comment: What is the point of an opt-in warning, when the entire point of the proposed warning is letting people know that they may be using something they are not fully educated or informed about the ramifications of using? If yo

[issue31742] Default to emitting FutureWarning for provisional APIs

2017-10-09 Thread Amber Brown
Amber Brown <hawk...@atleastfornow.net> added the comment: Donald hits it on the head for me. As long as the code is not covered by the same API deprecation contract that the rest of the standard library is, it should make it obvious when attempting to use it. I can be relatively c