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 Jim.Jewett, asvetlov, gpolo, serhiy.storchaka, terry.reedy
Date 2014-06-02.19:09:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1401736144.93.0.358206509288.issue6167@psf.upfronthosting.co.za>
In-reply-to
Content
1. In activate, change parameter 'index' to 'element'.  I agree with Jim about rejecting this. A (specific). 'index' is routinely used to point to an item in a sequence; "arrow1", "slider", and "arrow2" are visually sequenced. The doc string is clear on the possible indexes Text also uses words for indexes. B (general). we don't break code by renaming arguments; I am pretty sure that any exception one might raise does not apply to this issue.

2. Give index a default of None and return the result of calling tk with None, instead of tossing it. I believe this enhancement would make activate more consistent with other methods. If so, do it -- with an added test.

3. Give .set() specific parameters. I think the current docstring is a bit confusing and should be revised. Am I correct in thinking that on a vertical slider, the upper end get the lower value, whereas the lower end gets the higher value? And that one should call bar.set(.3, .6) rather than bar.set(.6, .3)? If so, calling the parameters 'lowval' and 'hival' might be clearer.

Does msg201484 mean that tk requires exactly 2 args? If so, some change seems ok. Deleting 'args' cannot in itself break code as 'args' cannot be used as a keyword. I agree with not adding defaults,
History
Date User Action Args
2014-06-02 19:09:04terry.reedysetrecipients: + terry.reedy, gpolo, asvetlov, Jim.Jewett, serhiy.storchaka
2014-06-02 19:09:04terry.reedysetmessageid: <1401736144.93.0.358206509288.issue6167@psf.upfronthosting.co.za>
2014-06-02 19:09:04terry.reedylinkissue6167 messages
2014-06-02 19:09:04terry.reedycreate