[issue36256] parser module fails on legal input

Xavier Combelle added the comment: never used the parser module nor lib2to3. Does they have any advantage over ast.parse and ast module ? -- ___ Python tracker <https://bugs.python.org/issue36

[issue36440] more helpful diagnostics for parser module

Change by Xavier Combelle : -- nosy: -xcombelle ___ Python tracker <https://bugs.python.org/issue36440> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue19024] Document asterisk (*), splat or star operator

Changes by Xavier Combelle : -- nosy: +xcombelle ___ Python tracker <http://bugs.python.org/issue19024> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue20197] Support WebP image format detection in imghdr module

Changes by Xavier Combelle : -- nosy: +xcombelle ___ Python tracker <http://bugs.python.org/issue20197> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue3849] FUD in documentation for urllib.urlopen()

Changes by Xavier Combelle : -- nosy: +xcombelle ___ Python tracker <http://bugs.python.org/issue3849> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue20891] PyGILState_Ensure on non-Python thread causes fatal error

Changes by Xavier Combelle : -- nosy: +xcombelle ___ Python tracker <http://bugs.python.org/issue20891> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue26363] __builtins__ propagation is misleading described in exec and eval documentation

Xavier Combelle added the comment: It is not the dictionary of builtin module, which is inserted in , but the current __builtin__ global which happen to be normally the dictionnary of builtin. Hence in the following code, the builtins propagation works has expected. >>> eval(&quo

[issue26363] __builtins__ propagation is misleading described in exec and eval documentation

Xavier Combelle added the comment: Hi Julien, You are fully right that it is the builtin module dictionnary which is inserted in eval or exec context. However, if a "__builtins__" entry is passed to eval or exec, this builtin module dictionnary is modified hence the following wor

[issue26363] __builtins__ propagation is misleading described in exec and eval documentation

Xavier Combelle added the comment: not an inconsisties but in the eval documentaion nothing specify that the builtins propagate between levels updates -- ___ Python tracker <http://bugs.python.org/issue26

[issue28962] Crash when throwing an exception with a malicious __hash__ override

Xavier Combelle added the comment: To my knowledge it is not the kind of arbitrary code which could segfault python code. It is far different for example that the fact by using bytecode magic you can segfault the interpreter, as this last case is explicitly warned in documentation

[issue25571] Improve the lltrace feature with the Py_Debug mode

Xavier Combelle added the comment: I made some comment on code in review. A thing that worry me that there is zero automated test. In my opinion the minimal should be to test the expected output. A nice to have would be a test for the write_contents function of makeopcodetranslations.py

[issue26526] In parsermodule.c, replace over 2KLOC of hand-crafted validation code, with a DFA

Xavier Combelle added the comment: The DFA is generated by other part of existing cpython code ? If it's the case looks like you did a great job. -- nosy: +xcombelle ___ Python tracker <http://bugs.python.org/is

[issue12345] Add math.tau

Xavier Combelle added the comment: Python will really follow the tau sort joke ? I never saw it mentioned in any serious math or programming document. All the github search result looks like people who are in this joke (kind of). The page http://tauday.com/state-of-the-tau list very little

[issue26415] Excessive peak memory consumption by the Python parser

Xavier Combelle added the comment: Looks that there is two bug as partial solution of the main bug which is reduce memory consumption of the parser: - The compression thing - the reducing of heap fragmentation Could each sub bug have it's own bug tracker and mark them blocking for the mai

[issue18595] zipfile: symlinks etc.

Xavier Combelle added the comment: about the readlink functionnality, I would like to point that it might lead to security issues see for example https://security.stackexchange.com/questions/73718/how-zip-symlink-works At least, the standard read should not do it by default. -- nosy

[issue26363] builtins propagation is misleading described in exec and eval documentation

Changes by Xavier Combelle : -- assignee: docs@python components: Documentation nosy: docs@python, xcombelle priority: normal severity: normal status: open title: builtins propagation is misleading described in exec and eval documentation ___ Python

[issue26363] __builtins__ propagation is misleading described in exec and eval documentation

New submission from Xavier Combelle: According to my experiment in code, the current behavior of python3.5 is different that the document says. If I understand well the purpose of this behavior is to propagate the __builtins__ global constant if globals has not one. In https