In several contexts, IDLE binds clicking of the right mouse button to context popup menus, most importantly, to provide the Set Breakpoint and Clear Breakpoint actions in edit windows.  On OS X systems, however, one cannot assume there will be more than one (e.g. the left) mouse button.  Further, Aqua Tk, the default on OS X, binds a right button if present to <Button-2>, rather than <Button-3> as with other Tk implementations and ignores <Button-3> bindings.  The net effect is that there is currently no way to use IDLE's breakpoint facility with Aqua Tk, with or without a multi-button mouse.

The attached patch modifies IDLE on OS X to bind popup menus to Control-Click (of the main or "left" button), as is commonly done elsewhere in OS X.

Platform consistency is a worthy criterion for changes, but I suspect such a behavior change can’t make it into stable branches.

IMO, it's not s behavior change, it's a serious bug in the OS X version as released in the python.org installer.  Important functionality is broken.

Apologies, I had misread your message: I thought the keybinding was wrong but working.  Your fix should be committed.

The patch binds the menu to Ctrl-Button-1 (that is, the way you open context menu's on OSX systems with a single button), however rightclick still doens't work (but does an X11-style paste operation).

I propose adding an explicit binding for button-2 as well:

            text.bind("<Control-Button-1>",self.right_menu_event)
            text.bind("<Button-2>",self.right_menu_event)

This ensures that the context menu can be opened using the expected mouse button.

An IMO additional bonus is that the odd X11-style pasting behaviour is disabled (that is, right-click is no longer equivalent to Cmd-V), although one could claim that this breaks backward compatibility.

Unfortunately, just adding the binding to <button-2> does not work because the Tk Text widget already has a documented binding of "paste-text" to <button-2> and this does not override that.  With the binding added, I found that the button-2 behavior for breakpoints did not work correctly as both events would be triggered and the resulting breakpoint lines were incorrect.  That, plus the compatibility issue, is why I thought it best to just stick to control-click.

Yet another prove of how much Tk sucks on OSX.

I'm not too happy about only binding Ctrl+<button-1>, because users will expect that this is means that <button-2> works as well. But if we cannot disable the default <button-2> binding we'll have to live with this crap.

Oops, 's/prove/proof/'

It could be worse.  As I noted in Issue10405, the IDLE breakpoint facility appears to be officially undocumented on any platform so it's hard to know what users' expectations are.  And there are still Macs out there with only one button.  As a side note, there are still OS X X11 versions of Tkinter for current Python releases; for example, the default MacPorts Tk configuration is X11-based; it does have the advantage of working without quirks in 64-bit builds.

I think this should be applied for 3.2 (and 2.7 and 3.1). The risk is low and the benefit to OS X IDLE users is great, since without it there is no way to use IDLE's breakpoint facility.

Looks fine, David, do you want to commit?

Committed to py3k in r87374, 3.1 in r87375, and 2.7 in r87376.