[issue18131] Tkinter Variables require a proper master

Serhiy Storchaka added the comment: And the first issue was fixed in issue42630. -- resolution: -> fixed stage: needs patch -> resolved status: open -> closed ___ Python tracker

[issue18131] Tkinter Variables require a proper master

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue18131] Tkinter Variables require a proper master

Serhiy Storchaka added the comment: > I am thinking that all uses of _default_root should raise something like > WhateverError("An explicit master is required when _default_root is None or > deleted.") Serhiy, what do you think? Technically all works (raises some exception), but I agree that er

[issue18131] Tkinter Variables require a proper master

Terry J. Reedy added the comment: My first message discussed two different issues. The first, generalized, is that unconditionally using tkinter._default_root, which can be either None or absent, as a backup for master=None in __init__ functions, seems a bit sloppy. Image.__init__ does this

[issue18131] Tkinter Variables require a proper master

Changes by Martin Panter : -- nosy: +vadmium ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue18131] Tkinter Variables require a proper master

Mark Lawrence added the comment: Just a gentle reminder. -- nosy: +BreamoreBoy versions: +Python 3.5 -Python 3.3 ___ Python tracker ___ __

[issue18131] Tkinter Variables require a proper master

New submission from Terry J. Reedy: The signature for tkinter class Variable and its subclasses StringVar, IntVar, DoubleVar, BooleanVar is def __init__(self, master=None, value=None, name=None): However, the None default is invalid because of self._tk = master.tk The preceding lines