[issue25021] product_setstate() Out-of-bounds Read

Roundup Robot added the comment: New changeset 8cc052c28910 by Kristján Valur Jónsson in branch '3.3': Issue #25021: Correctly make sure that product.__setstate__ does not access https://hg.python.org/cpython/rev/8cc052c28910 New changeset 4f85b6228697 by Kristján Valur Jónsson in branch '3.4':

[issue25021] product_setstate() Out-of-bounds Read

Changes by Kristján Valur Jónsson : -- stage: -> resolved ___ Python tracker ___ ___

[issue24965] Implement PEP 498: Literal String Formatting

Eric V. Smith added the comment: I'll probably ensure that all of the parsing errors contain "format string" or "f-string" or similar. That way the regex check is easier, and the user can search for it more easily. It remains to be seen how these are referenced in the documentation.

[issue24965] Implement PEP 498: Literal String Formatting

Eric V. Smith added the comment: After discussing it with Guido, I've removed the ability to combine 'f' with 'u'. -- ___ Python tracker ___

[issue23992] multiprocessing: MapResult shouldn't fail fast upon exception

Davin Potts added the comment: As an aside: issue24948 seems to show there are others who would find the immediate-multiple-error_callback idea attractive. -- ___ Python tracker

[issue20917] Idle: Enhance font change notification system

Mark Roseman added the comment: The new 'component' infrastructure provides the mechanism for passing these kinds of notifications around. Allowing extensions (in whatever form they'll exist with the new stuff) to take part in this notification mechanism would be a small (and sensible)

[issue24965] Implement PEP 498: Literal String Formatting

Jelle Zijlstra added the comment: Thanks! Here are a few more cases I came across with the existing implementation: >>> f"{'a\\'b'}" File "", line 1 SyntaxError: missing '}' in format string expression I believe this is valid and should produce "a'b". >>> f"{x!s!s}" File "", line 1

[issue24948] Multiprocessing not timely flushing stack trace to stderr

Davin Potts added the comment: If I understand your motivations correctly, I'd restate them as: you want a mechanism for being immediately notified of an exception in a parent process without waiting on any child processes of that parent to finish and furthermore propose this should be the

[issue24862] subprocess.Popen behaves incorrect when moved in process tree

Andre Merzky added the comment: This is patch is meant to be illustrative rather than functional (but it works in the limited set of cases I tested). -- keywords: +patch Added file: http://bugs.python.org/file40448/subprocess.py.diff ___ Python

[issue24965] Implement PEP 498: Literal String Formatting

Jelle Zijlstra added the comment: Is this behavior intentional? >>> str = len >>> x = 'foo' >>> f'{x!s}' '3' >>> '{!s}'.format(x) 'foo' Or similarly: >>> import builtins >>> del builtins.repr >>> f'{x!r}' Traceback (most recent call last): File "", line 1, in NameError: name 'repr' is not

[issue24965] Implement PEP 498: Literal String Formatting

Jelle Zijlstra added the comment: I've started working on implementing this feature in Cython and I'd like to confirm a few edge cases: - f'{ {1: 2\N{RIGHT CURLY BRACKET}[1]}' == '2' (string escape rules work even within the expressions) - f'{ '''foo''' }' is a syntax error - f'{ """foo

[issue24965] Implement PEP 498: Literal String Formatting

Eric V. Smith added the comment: This patch fixes triple-quoted strings, plus a few bugs. I'm going to commit it tomorrow, barring any unforeseen issues. -- Added file: http://bugs.python.org/file40447/pep-498-5.diff ___ Python tracker

[issue24862] subprocess.Popen behaves incorrect when moved in process tree

Andre Merzky added the comment: Yes, I have a workaround (and even a clean solution) in my code. My interest in this ticket is more academic than anything else :) Thanks for the pointer to issue1731717. While I am not sure which 'comment at the end' you exactly refer to, the whole

[issue24965] Implement PEP 498: Literal String Formatting

Eric V. Smith added the comment: Yes, Jelle, you are correct in all 3 cases. Remember that the steps are to extract the string from the source code, decode backslash escapes, and only then treat it as an f-string. For the first case, without the 'f' prefix: '{ {1: 2\N{RIGHT CURLY

[issue24965] Implement PEP 498: Literal String Formatting

Eric V. Smith added the comment: Agreed on checking the error messages better. Especially since even the simplest of errors (like leaving out a quote) results in a syntax error in parsing the string, not parsing inside the f-string. I'll look at it eventually. --

[issue24965] Implement PEP 498: Literal String Formatting

Martin Panter added the comment: Regarding wrong error messages, I’ve learnt the hard way that it is often best to use assertRaisesRegex() instead of assertRaises(), to ensure that the actual exception you have in mind is being triggered, rather than a typo or something. Though that might

[issue24965] Implement PEP 498: Literal String Formatting

Eric V. Smith added the comment: This one has been fixed: >>> f"{'a\\'b'}" "a'b" This one was a bug that I previously fixed, that Martin pointed out: >>> f"{x!s!s}" File "", line 1 SyntaxError: invalid character following conversion character And this is the same bug: >>> f"{x!s{y}}" File

[issue24899] Add an os.path <=> pathlib equivalence table in pathlib docs

Nikita Klimov added the comment: I make a correlation table, plan to finish by September 16 or earlier -- ___ Python tracker ___

[issue25070] Python 2.6 - Python 3.4 allows unparenthesized generator with *args, **kw, forbidden in 3.5

Roundup Robot added the comment: New changeset 10a9d4acd9cb by Yury Selivanov in branch '3.5': whatsnew/3.5 More edits https://hg.python.org/cpython/rev/10a9d4acd9cb -- nosy: +python-dev ___ Python tracker

[issue24948] Multiprocessing not timely flushing stack trace to stderr

Changes by Davin Potts : -- type: -> behavior ___ Python tracker ___ ___

[issue25070] Python 2.6 - Python 3.4 allows unparenthesized generator with *args, **kw, forbidden in 3.5

Yury Selivanov added the comment: What's new is now updated with description of this issue. Closing it now. -- resolution: -> wont fix stage: -> resolved status: open -> closed ___ Python tracker

[issue24948] Multiprocessing not timely flushing stack trace to stderr

Changes by Davin Potts : -- nosy: +jnoller, sbt ___ Python tracker ___ ___

[issue25036] IDLE - infrastructure changes so editors don't assume they're in a toplevel

Mark Roseman added the comment: FYI, I've gone past this point in my own playground, to the point of having a working tabbed editor implementation. It's not that much further actually. Here are the next steps: 1. Change so that Container is passed to Components on creation, rather than

[issue24862] subprocess.Popen behaves incorrect when moved in process tree

Changes by Andre Merzky : Removed file: http://bugs.python.org/file40448/subprocess.py.diff ___ Python tracker ___

[issue24862] subprocess.Popen behaves incorrect when moved in process tree

Changes by Andre Merzky : Added file: http://bugs.python.org/file40449/subprocess.py.diff ___ Python tracker ___

[issue25076] Wrong parameter name in distutils documentation

Roundup Robot added the comment: New changeset 1208c85af6d5 by Benjamin Peterson in branch '3.4': fix name of argument in docstring and the docs (closes #25076) https://hg.python.org/cpython/rev/1208c85af6d5 New changeset 63bbe9f80909 by Benjamin Peterson in branch '2.7': fix name of argument

[issue25021] product_setstate() Out-of-bounds Read

Changes by Raymond Hettinger : -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue25081] Windows installer Upgrade->Customize->Back goes to Install page

New submission from Steve Dower: If you already have Python 3.5.0b4 or later installed and you go to install a later version, it starts with an "Upgrade" page. If you hit customize from the page, then Back, you end up at the original Install page. You should be at the Customize page.

[issue24965] Implement PEP 498: Literal String Formatting

Eric V. Smith added the comment: Both of those are known (to me!) byproducts of the current implementation. If my crazy idea of adding opcodes to speed up f-strings flies, then this issue will go away. I consider this a corner case that doesn't need to be addressed before committing this

[issue24965] Implement PEP 498: Literal String Formatting

Martin Panter added the comment: I’m actually trying out your patch now. A couple strange errors and observations: >>> f"{'{'}" # Why is this allowed in an outer format expression-- '{' >>> f"{3:{'{'}>10}" # --but not inside a format specifier? SyntaxError: nesting of '{' in format specifier

[issue25077] Compiler warnings: initialization from incompatible pointer type

New submission from Marius Gedminas: I'm seeing these compiler warnings while trying to build Python 3.5 on Ubuntu 15.04: In file included from Python/ceval.c:300:0: Python/ceval_gil.h: In function ‘drop_gil’: Python/ceval_gil.h:181:144: warning: initialization from incompatible pointer type

[issue16473] quopri module differences in quoted-printable text with whitespace

Serhiy Storchaka added the comment: Mentioned functions are not exact equivalents of codecs. They are preferable way to to obtain the similar (apart from minor details) output. -- nosy: +ncoghlan, serhiy.storchaka ___ Python tracker

[issue25078] Document InstallAllUsers installer parameter default 0

New submission from Thomas Kluyver: In testing the 3.5.0rc4 default installer, I found that the default for InstallAllUsers appears to be 0, whereas it's currently documented as 1. -- assignee: docs@python components: Documentation files: installallusers-default.patch keywords: patch

[issue25079] Tokenize generates NL instead of NEWLINE for comments

New submission from Optimal BPM: Quoting the documentation: tokenize.NL Token value used to indicate a non-terminating newline. The NEWLINE token indicates the end of a logical line of Python code; NL tokens are generated when a logical line of code is continued over multiple physical lines.

[issue25027] Python 3.5.0rc3 on Windows can not load more than 127 C extension modules

Larry Hastings added the comment: Pull request accepted. Please forward-merge, thanks! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue23992] multiprocessing: MapResult shouldn't fail fast upon exception

Davin Potts added the comment: The patches make good sense to me -- I have no comments to add in a review. I spent more time than I care to admit concerned with the idea that error_callback (exposed by map_async which map sits on top of) should perhaps be called not just once at the end but

[issue23992] multiprocessing: MapResult shouldn't fail fast upon exception

Changes by Davin Potts : -- stage: needs patch -> patch review ___ Python tracker ___

[issue22980] C extension naming doesn't take bitness into account

Larry Hastings added the comment: It's fixed! So it's finally closed. -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker

[issue25007] Add support of copy protocol to zlib compressors and decompressors

shiyao.ma added the comment: per serhiy's suggestion, added two aliases. -- keywords: +patch nosy: +introom Added file: http://bugs.python.org/file40446/patch.diff ___ Python tracker

[issue25080] The example-code for making XLM-RPC requests through proxy, fail!

New submission from Kostis ankostis: The example code provided at the bottom of the reference-page: https://docs.python.org/2/library/xmlrpclib.html#example-of-client-usage for making XML-RPC requests through a proxy by defining a custom transport fails (at least) in python-3.4! Obviously

[issue25070] Python 2.6 - Python 3.4 allows unparenthesized generator with *args, **kw, forbidden in 3.5

Stefan Krah added the comment: I think the issue can be closed (after updating "what's new"). Even if we wanted to keep backwards compatibility, it's too late now. -- ___ Python tracker

[issue25079] Tokenize generates NL instead of NEWLINE for comments

Stefan Krah added the comment: See: https://docs.python.org/3/reference/lexical_analysis.html#blank-lines -- assignee: -> docs@python components: +Documentation -Interpreter Core nosy: +docs@python, skrah resolution: -> not a bug stage: -> resolved status: open -> closed type:

[issue16473] quopri module differences in quoted-printable text with whitespace

Martin Panter added the comment: The list of functions were added in Issue 17844. I made the change today because I forgot that the listed functions weren’t exactly equivalent when investigating Issue 25075. Base64-codec encodes to multiple lines, but b64encode() returns the raw encoding