Jan-07-2018, 06:34 AM
I don't believe that your suggested reason is a good reason at all. The problem is not that two lines of code need are needed but that a user needs to realize the requirement and to put in the lines repeatedly. It takes a fair amount of time to comb the skimpy documentation to find the requirement. Multiply the inconvenience by the number of users and it adds up; it's not a matter of refusing to install PIL, it is an annoyance particularly when one is learning Tkinter and probably Tk. The Tk folks thought it useful enough to include and I am glad they did. I hope the Tkinter maintainers are not satisfied with a partial interface to Tk.
Pushing the argument about duplicating functionality would lead to the complete removal of PhotoImage since it could be entirely replaced by PIL. I think that is the case but I cannot find definitive documentation of PhotoImage.
A very canny programmer I knew maintained that "The hallmark a good tool is that it be a delight to use". When PhotoImage doesn't handle a most common case it fails that criteria. And it impacts the building of tools based on Tkinter.
How does one make a feature request or bug report?
Pushing the argument about duplicating functionality would lead to the complete removal of PhotoImage since it could be entirely replaced by PIL. I think that is the case but I cannot find definitive documentation of PhotoImage.
A very canny programmer I knew maintained that "The hallmark a good tool is that it be a delight to use". When PhotoImage doesn't handle a most common case it fails that criteria. And it impacts the building of tools based on Tkinter.
How does one make a feature request or bug report?