[Python-Dev] Possible problem that may be caused by Tkinter renaming (original) (raw)
Guilherme Polo ggpolo at gmail.com
Sat May 17 22:53:32 CEST 2008
- Previous message: [Python-Dev] Possible problem that may be caused by Tkinter renaming
- Next message: [Python-Dev] oct and hex Py3k warnings
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2008/5/17 Guilherme Polo <ggpolo at gmail.com>:
Hello,
I smell a problem caused by this line at tkinter/init.py: tkinter = tkinter # b/w compat for export
Georg and me decided to remove that line as a solution to this problem.
This was fine when tkinter was a Tkinter module, but I believe it would be better to rename this to something else. Given that python has a lot of users, I'm sure you will be able to find all sort of crazy things over the internet and one of them could be: import tkinter from tkinter import * something = tkinter.defaultroot Which is not that crazy at all, for some values of crazy, but will fail now.
Regards, -- -- Guilherme H. Polo Goncalves
-- -- Guilherme H. Polo Goncalves
- Previous message: [Python-Dev] Possible problem that may be caused by Tkinter renaming
- Next message: [Python-Dev] oct and hex Py3k warnings
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]