[issue34455] Tkinter crashing when pressing Command + ^ (OSX)

2019-10-03 Thread Aivar Annamaa
Aivar Annamaa added the comment: > to conditionallly bind '' to a function that returns 'break' I tried capturing all events. The handler was called for Cmd press, but the crash occurred before the handler was called for the other key. -- ___

[issue38350] ./configure --with-pydebug should use -O0 rather than -Og

2019-10-03 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: The purpose of using -Og is that it significantly speeds up tests. You can always pass CFLAGS="-O0" if you debug particular debugger issues, but in normal cases -Og looks more beneficial. It saves hours of time of common developers. --

[issue34455] Tkinter crashing when pressing Command + ^ (OSX)

2019-10-03 Thread Terry J. Reedy
Terry J. Reedy added the comment: Aivar, thank you for opening the issue. I believe what I meant about tkinter bind calls would be to conditionallly bind '' to a function that returns 'break', thus claiming that the key combination has been handled and that tk should ignore it. The

[issue38106] [2.7] Race in PyThread_release_lock on macOS - can lead to memory corruption and deadlock

2019-10-03 Thread Kirill Smelkov
Kirill Smelkov added the comment: :) Yes and no. PyPy did not make a new release with the fix yet. -- ___ Python tracker ___ ___

[issue38106] [2.7] Race in PyThread_release_lock on macOS - can lead to memory corruption and deadlock

2019-10-03 Thread STINNER Victor
STINNER Victor added the comment: > PyPy people fixed the bug the same day it was reported: ... Oh ok, so the CPython commit message is already outdated :-) "PyPy has the same bug for both pypy2 and pypy3 (...)" -- ___ Python tracker

[issue38106] [2.7] Race in PyThread_release_lock on macOS - can lead to memory corruption and deadlock

2019-10-03 Thread Kirill Smelkov
Kirill Smelkov added the comment: Victor, thanks for merging. > I'm surprised that we still find new bugs in this code which is supposed to > be battle tested! Maybe recent Darwin changed made the bug more likely. As discussed above (https://bugs.python.org/issue38106#msg351917,

[issue36670] regrtest: win_utils decodes typeperf output from the wrong encoding (test suite broken due to cpu usage feature on win 10/ german)

2019-10-03 Thread STINNER Victor
Change by STINNER Victor : -- pull_requests: +16141 stage: resolved -> patch review pull_request: https://github.com/python/cpython/pull/16553 ___ Python tracker ___

[issue37373] Configuration of windows event loop for libraries

2019-10-03 Thread Nathaniel Smith
Nathaniel Smith added the comment: It's also possible to implement 'select' on top of IOCP using undocumented private APIs. That's what libuv does (and how 'select' works internally). There's a bunch of information on this collected here: https://github.com/python-trio/trio/issues/52

[issue38350] ./configure --with-pydebug should use -O0 rather than -Og

2019-10-03 Thread STINNER Victor
STINNER Victor added the comment: > Do note though that if the -D_FORTIFY_SOURCE=2 hardening flag is used, the > compilation will fail with an optimization level less than -Og. Does it make any sense to use a debug build in production? Does it make sense to enable hardening on a debug

[issue38106] [2.7] Race in PyThread_release_lock on macOS - can lead to memory corruption and deadlock

2019-10-03 Thread STINNER Victor
STINNER Victor added the comment: I merged Kirill Smelkov's fix. Thanks. I close the issue. I'm surprised that we still find new bugs in this code which is supposed to be battle tested! Maybe recent Darwin changed made the bug more likely. PyPy: it's now your turn to fix it ;-) --

[issue38106] [2.7] Race in PyThread_release_lock on macOS - can lead to memory corruption and deadlock

2019-10-03 Thread STINNER Victor
STINNER Victor added the comment: New changeset c5abd63e94fcea10bdfa7a20842c6af3248bbd74 by Victor Stinner (Kirill Smelkov) in branch '2.7': bpo-38106: Fix race in pthread PyThread_release_lock() (GH-16047) https://github.com/python/cpython/commit/c5abd63e94fcea10bdfa7a20842c6af3248bbd74

[issue38333] add type signatures to library function docs

2019-10-03 Thread paul rubin
paul rubin added the comment: I don't think we're going to accomplish anything continuing the eternal static-vs-dynamic debate, which in Python's case has already been resolved by adding optional static typing. It's a done deal, and the issue here is just how to document it. Erlang (via

[issue38333] add type signatures to library function docs

2019-10-03 Thread Vedran Čačić
Vedran Čačić added the comment: Your arguments in my view boil down to "Haskell is a nice language" and "Static typing is useful". It still doesn't change my argument that Python is genetically neither of these. And we will cripple it greatly if we try to push it in that direction. [Your

[issue38333] add type signatures to library function docs

2019-10-03 Thread paul rubin
paul rubin added the comment: At first glance, having a typeclass for each protocol (at least the widely used ones) seems fine. It's inherent in Haskell and a lot of libraries are organized around a common set of typeclasses--look up "Typeclassopedia" for descriptions of them. Certainly

[issue34455] Tkinter crashing when pressing Command + ^ (OSX)

2019-10-03 Thread Aivar Annamaa
Aivar Annamaa added the comment: I created the ticket: https://core.tcl-lang.org/tk/tktview/5849df7852c48cb763b11a11d848a68482b0f828 -- nosy: +Aivar.Annamaa ___ Python tracker

[issue38333] add type signatures to library function docs

2019-10-03 Thread Vedran Čačić
Vedran Čačić added the comment: Well, yes, if you're going to invent a special typeclass for every protocol, then you can document any signature. But what purpose does it serve? Abs to me seems like a hack, not something we really wanted to capture with the type system. Do you find (x :

<    1   2