➜

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-21.16:58:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1506013113.44.0.751753357298.issue31547@psf.upfronthosting.co.za>
In-reply-to
Content 
User keysets are saved as a complete keyset, but users could edit the file and delete event-sequence pairs or add an incomplete set.  When a keyset is used, default pairs are added for any that are missing, if the pair does not conflict with existing pairs.

When extensions were converted to features #27099, 8 new pairs were added to the 'complete' set.  All user keyset are missing these pairs.  I expect that other pairs will be added in the future.  I propose that augmented keysets should be written back to the file, with notice to the user.

Detail: check when read or when used?  All keysets are written, so fix all?
History
Date User Action Args
2017-09-21 16:58:33terry.reedysetrecipients: + terry.reedy
2017-09-21 16:58:33terry.reedysetmessageid: <1506013113.44.0.751753357298.issue31547@psf.upfronthosting.co.za>
2017-09-21 16:58:33terry.reedylinkissue31547 messages
2017-09-21 16:58:33terry.reedycreate