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 | isandler |
|---|---|
| Recipients | isandler, loewis |
| Date | 2008年02月22日.01:53:15 |
| SpamBayes Score | 0.015108455 |
| Marked as misclassified | No |
| Message-id | <1203645197.43.0.103807687202.issue2059@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
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 Tkinter.Canvas >> import Tix.ComboBox #whoops, we've got Tix's combobox Tix.ComboBox As a matter of fact, Tix docs seem to explicitly recommend accessing Tkinter stuff through Tix: """The former imports the latter, so to use Tix with Tkinter, all you need to do is to import one module. In general, you can just import Tix, and replace the toplevel call to Tkinter.Tk with Tix.Tk""" |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年02月22日 01:53:17 | isandler | set | spambayes_score: 0.0151085 -> 0.015108455 recipients: + isandler, loewis |
| 2008年02月22日 01:53:17 | isandler | set | spambayes_score: 0.0151085 -> 0.0151085 messageid: <1203645197.43.0.103807687202.issue2059@psf.upfronthosting.co.za> |
| 2008年02月22日 01:53:16 | isandler | link | issue2059 messages |
| 2008年02月22日 01:53:15 | isandler | create | |