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 terry.reedy
Recipients terry.reedy
Date 2017-09-11.03:17:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1505099853.11.0.427045328648.issue31414@psf.upfronthosting.co.za>
In-reply-to
Content
Test_configdialog 'tests' several integer entry widgets by inserting a digit and then checking that the new value was sent to changes.  However, users may delete an entry totally and enter a new value.  If we associate an IntVar with the entry widget, int('') is called somewhere in the process, which raises.  (IntVar(root).set('') does not, so the error is somewhere further along.  The test should imitate users by delete and insert.

Note: a deeper problem is attaching a tracer that get called with each keystroke.  Using a StringVar avoids the error when the entry is blanked, but currently allows non-ints to be saved.  A better solution would be to not do the auto tracing, but use a IntVar and only call var_changed when the user 'leaves' the box, after checking for a count in a sane range.
History
Date User Action Args
2017-09-11 03:17:33terry.reedysetrecipients: + terry.reedy
2017-09-11 03:17:33terry.reedysetmessageid: <1505099853.11.0.427045328648.issue31414@psf.upfronthosting.co.za>
2017-09-11 03:17:33terry.reedylinkissue31414 messages
2017-09-11 03:17:32terry.reedycreate