You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee='https://github.com/terryjreedy'closed_at=<Date2017-07-11.07:50:23.446>created_at=<Date2017-07-11.07:05:27.549>labels= ['expert-IDLE', '3.7', 'invalid']
title='IDLE: Fix configdialog should use wm_withdraw'updated_at=<Date2017-07-11.07:56:46.298>user='https://github.com/mlouielu'
Introduce in bpo-30728, commit bac7d33, self.wm_withdraw has been changed into self.withdraw. This make bpo-30870 un-testable since it using self.withdraw will block out event_generate.
This issue revert self.widthdraw to self.wm_withdraw.
Color me dubious ;-). The change was made because tkinter.__init__, line 1990 has this line
withdraw = wm_withdraw
There is a similar line for all of the around 30 wm_xyz functions. Prefixing the names of methods of class Wm is an unusual redundancy. I cannot think of any sane way for tk to know which python synonym was used to call the Python wrapper.
What code using event_generate led you to this conclusion?
Hmmm, I think it is a mistake of my test, it is something inside configdialog init make unittest can't do event_generate, but not this one self.withdraw.
I first beat my head against event_generate two or three years ago. So I appreciate you taking a whack at it. It is nice that Variable.set and invoke can be used for tests, but it would really be nice to have e_v work too.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: