This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author epaine
Recipients RhinosF1, epaine, serhiy.storchaka, shippo_
Date 2020-12-27.12:35:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
See also issue41851. I personally think that being able to compare whether two tkinter variables point to the same Tk variable is very useful so needs to stay in some form. However, I don't see any situation where comparing to see if two tkinter variables are the same Python object would be helpful.

Comparing to a list (for example), `assert a is b` would mean altering one would affect the other (while this is true of tkinter variables, to cover all cases you would instead check whether they are 'equal'). Therefore, while writing `a.get() == b.get()` isn't too bad, the point of this change would be consistency more than anything else (as-per the title).
Date User Action Args
2020-12-27 12:35:52epainesetrecipients: + epaine, serhiy.storchaka, shippo_, RhinosF1
2020-12-27 12:35:52epainesetmessageid: <>
2020-12-27 12:35:52epainelinkissue42750 messages
2020-12-27 12:35:52epainecreate