[issue20948] -Wformat=2 -Wformat-security findings

Martin Panter added the comment: GCC’s -Wformat options are documented at . We already enable -Wall by default, which implicitly enables -Wformat, but not -Wformat=2. Apparently, -Wformat=2 enables -Wformat-security, so

[issue26851] android compilation and link flags

Xavier de Gaye added the comment: New patch. The sed commands used to evaluate ANDROID_API_LEVEL and _arm_arch do not need to discard comment lines and empty lines in the output of the preprocessor. -- Added file: http://bugs.python.org/file43893/build-flags_4.patch __

[issue20948] -Wformat=2 -Wformat-security findings

Serhiy Storchaka added the comment: Seems warnings are gone after adding the const qualifier to static constant arrays (issue25923). -- ___ Python tracker ___ __

[issue26462] Patch to enhance literal block language declaration

Julien added the comment: @martin I reviewed my changes on `decimal.rst` and I now just fixing the indentation problem, so I don't change anything unrealated to fixing warnings, and don't break doctests. -- ___ Python tracker

[issue26462] Patch to enhance literal block language declaration

Julien added the comment: Here a new patch after reviewing comments on rietveld. -- Added file: http://bugs.python.org/file43892/issue26462.v5.diff ___ Python tracker ___ ___

[issue20948] -Wformat=2 -Wformat-security findings

Jeffrey Walton added the comment: On Tue, Jul 26, 2016 at 4:31 AM, Martin Panter wrote: > > Martin Panter added the comment: > > The Modules/main.c cases are not errors. They are just long strings defined > as static constants, rather than literals passed in directly. > > I think we can close t

[issue17238] IDLE: Add import statement completion

Martin Panter added the comment: The readline completion code does not strictly depend on on Readline, although currently it is modelled after its quirky API. But we can change that by adding a more general API. In , I suggested an API “complete_c

[issue20948] -Wformat=2 -Wformat-security findings

Martin Panter added the comment: The Modules/main.c cases are not errors. They are just long strings defined as static constants, rather than literals passed in directly. I think we can close this now. Unless people think this warning is worth using, in which case we should find a way to work

[issue27612] socket.gethostbyname resolving octal IP addresses incorrectly

Ronald Oussoren added the comment: For what it is worth: the relevant standard says that octal and hexadecimal addresses should be accepted (POSIX getaddrinfo refers to inet_addr for numeric IP addresses and that says that octal and hexadecimal numbers are valid in IP addresses), see: http://

[issue27621] incorrectly works in IDLE Query dialogs

Serhiy Storchaka added the comment: I have wrote similar patch. There are many ways to fix this issue. Tk code for dialog widgets is more complex and general. -- keywords: +patch Added file: http://bugs.python.org/file43891/idle_query_press_return.patch

[issue27620] IDLE: Add keyboard equivalents for mouse actions.

Serhiy Storchaka added the comment: I agree that Esc should always cancel regardless of where the focus is. -- nosy: +serhiy.storchaka ___ Python tracker ___

[issue27612] socket.gethostbyname resolving octal IP addresses incorrectly

koobs added the comment: @David The symptoms from FreeBSD look a little different: Only gethostbyname affected only on 2.7 and 3.3 on all freebsd versions (9, 10, 11). Python 3.2 was not tested (freebsd port was deleted), but likely affected as well Feels/Appears like a gethostbyname fix

[issue27621] incorrectly works in IDLE Query dialogs

Terry J. Reedy added the comment: I made this a dependency of #27620. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue27621] incorrectly works in IDLE Query dialogs

Terry J. Reedy added the comment: While writing #27620 and adding a binding to Query for , a few hours ago, I realized that this would be the case, that it could be considered a bug, and that the fix will be a 'return' function that looks at the focus before invoking [Ok] (the default) or [Can

[issue27622] int.to_bytes(): docstring is not precise

Serhiy Storchaka added the comment: The docstring looks correct to me. The last phrase corresponds to the last paragraph that describes the signed keyword-only argument. Is there anyone else for whom the docstring looks wrong? -- ___ Python tracker

[issue26638] Avoid warnings about missing CLI options when building documentation

Changes by Martin Panter : Added file: http://bugs.python.org/file43889/doc-warnings.v3.patch ___ Python tracker ___ ___ Python-bugs-list mail

[issue27622] int.to_bytes(): docstring is not precise

INADA Naoki added the comment: @mmarkk Do you read full docstring? It's documented very clearly. --- int.to_bytes(length, byteorder, *, signed=False) -> bytes Return an array of bytes representing an integer. The integer is represented using length bytes. An OverflowError is raised if the i

[issue27622] int.to_bytes(): docstring is not precise

Марк Коренберг added the comment: So, in order to make documentation consistent, either new text should be added, or last phraze removed. That's what I think. -- ___ Python tracker

<    1   2