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 aoi.leslie
Recipients aoi.leslie, gpolo, terry.reedy
Date 2011-12-03.03:35:56
SpamBayes Score 1.0355861e-10
Marked as misclassified No
Message-id <1322883357.72.0.314549261599.issue13519@psf.upfronthosting.co.za>
In-reply-to
Content
Setting the config has no problem. Only reading has.

The config is read from Tk at line 1270 by code

            res = self.tk.call('grid',
                       command, self._w, index)

. If each of the four options (minsize, pad, uniform, and weight) has been set to value 1, |res|'s value after the tk call would be a tuple |('-minsize', 1, '-pad', 1, '-uniform', '1', '-weight', 1)|. This explains why |uniform|'s value does not cause problem, because it is a str, while the other three's are int. Also int 0 does not cause problem because it is handled at line 1277 by code

                if not value:
                    value = None

so the resulting option value appears as None in rowconfigure or columnconfigure's resulting dict.

In my speculation, the bug is that, when converting from the tuple returned by tk call into the resulting dict to be returned by rowconfigure or columnconfigure, the converting code assumes that the option values in the tuple returned by tk call are all str. But somehow only |uniform|'s value is str, while other three's are int.
History
Date User Action Args
2011-12-03 03:35:57aoi.lesliesetrecipients: + aoi.leslie, terry.reedy, gpolo
2011-12-03 03:35:57aoi.lesliesetmessageid: <1322883357.72.0.314549261599.issue13519@psf.upfronthosting.co.za>
2011-12-03 03:35:57aoi.leslielinkissue13519 messages
2011-12-03 03:35:56aoi.lesliecreate