[issue3405] Add support for the new data option supported by event generate (Tk 8.5)

2011-01-31 Thread O.C.
O.C. added the comment: Hello, I read the proposed patch "event_generate__data2.diff" and the Tcl/Tk manual http://www.tcl.tk/man/tcl8.5/TkCmd/bind.htm#M24 * Could you please also add a field "e.user_data" ? This would simply be a copy of 'd' : --- e.det

[issue11194] "lock.__exit__ == lock.release" should be False

2011-02-11 Thread O.C.
New submission from O.C. : Hello, if 'lock' is a threading.Lock, the functions lock.__exit__() and lock.release() are different. The former takes 3 arguments, while the latter takes no argument. However, "lock.__exit__ == lock.release" returns True. Shouldn't it ret

[issue11194] "lock.__exit__ == lock.release" should be False

2011-02-11 Thread O.C.
O.C. added the comment: > Do you have a use case that this impacts? No, I can live with it. It was rather a point about clarity and consistency. For example, the difference between Lock and RLock: lock.__exit__==lock.release-> True rlock.__exit__==rlock.release -> False We cam

[issue3405] Add support for the new data option supported by event generate (Tk 8.5)

2012-07-11 Thread O.C.
O.C. added the comment: I don't agree with this comment. 1) The 'detail' field also contains a string, one of the following: "NotifyAncestor", "NotifyNonlinearVirtual",... 2) When an event is received, the 'detail' and 'user_data'