You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't think it will affect the usability when strings are used instead of integers.
When Tkinter expects a number (ie: row=3), it still works fine with row="3" given as a string.
I believe the reason it's fine with strings when it's expecting a number is because Tkinter uses TCL under the hood, and apparently in TCL everything is a string.
I'm not a TCL expert by any stretch, but that seems to be the most logical explanation I can think of as to why Tkinter works fine with integers and also strings.
Yes, it works just fine with strings, because Tkinter translates every object to string under the hood anyway.
But it's just more Pythonic to use integers instead of string everywhere.
sample output
The keyword arguments should be integers instead of strings.
The text was updated successfully, but these errors were encountered: