[issue2059] OptionMenu class is defined both in Tkinter and Tix

Sean Reifschneider <[EMAIL PROTECTED]> added the comment: I don't see the problem with the example listed in the last message. It sounds like the Tix documentation is confirming that this is the desired behavior. -- nosy: +jafo priority: -> normal resolution: -> works for me status: o

[issue2059] OptionMenu class is defined both in Tkinter and Tix

Ilya Sandler added the comment: I understand your argument. Yet, I am not sure classes with the same name are reasonable here. Tix is too intertwined with Tkinter: E.g a Tix user user can just access Tkinter widgets via Tix: >>> import Tix >>> print Tix.Canvas # This is TkInter's widget Tkint

[issue2059] OptionMenu class is defined both in Tkinter and Tix

Martin v. Löwis added the comment: What is the issue that you are reporting here? There is nothing wrong with two classes having the same name, AFAICT. That's what modules are for. -- nosy: +loewis __ Tracker <[EMAIL PROTECTED]>

[issue2059] OptionMenu class is defined both in Tkinter and Tix

New submission from Ilya Sandler: Given that Tix imports all names from Tkinter this is likely to result in confusion. E.g. >>> from Tix import * >>> print Button Tkinter.Button >>> print OptionMenu Tix.OptionMenu To get to Tkinter's OptionMenu, one needs to do something like import Tkinter T