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 roger.serwy
Recipients George.Dhoore, asvetlov, ned.deily, roger.serwy, terry.reedy
Date 2012-03-31.17:10:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1333213856.06.0.578204552137.issue11437@psf.upfronthosting.co.za>
In-reply-to
Content
Without the known_invalid list, each call to GetCurrentKeySet would cause an error message to appear. The effect of keeping track of these bad key bindings is that the user receives a notification only once about a particular bad key binding. (The present architecture in IDLE calls GetCurrentKeySet too many times during initialization.)

The known_invalid list gets extended with any newly found invalid key bindings. Also, these newly found invalid keys generates an error message. This can occur again if the user modifies the key map with the configuration dialog.

Perhaps using a set instead of a list would make the code clearer.
History
Date User Action Args
2012-03-31 17:10:56roger.serwysetrecipients: + roger.serwy, terry.reedy, ned.deily, asvetlov, George.Dhoore
2012-03-31 17:10:56roger.serwysetmessageid: <1333213856.06.0.578204552137.issue11437@psf.upfronthosting.co.za>
2012-03-31 17:10:55roger.serwylinkissue11437 messages
2012-03-31 17:10:55roger.serwycreate