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 markroseman
Recipients kbk, markroseman, roger.serwy, terry.reedy
Date 2015-10-04.18:56:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1443984999.04.0.662978641564.issue25313@psf.upfronthosting.co.za>
In-reply-to
Content
Actually, I think we may be able to get away without the warning message when you select a 'new' theme, and still maintain backwards compatibility.

For 'new' themes (i.e. IDLE Dark and any more builtins we add in the future), we write the theme out to the user configuration file, keeping the same name, and perhaps adding an extra field, i.e. 'builtin=1', so that we can recognize it in newer versions, along with a comment if possible.

The existing code looks up theme names by checking if its in the default list, and if not, looks in the user list. For older versions without IDLE Dark, it will then find it in the user list.

Besides writing out the theme to user config file, the only other change that would be needed in the code is to modify GetSectionList so that when it's looking in a user config file, it doesn't include sections that either have the builtin=1 from above, or just have the same name as things in the default file.
History
Date User Action Args
2015-10-04 18:56:39markrosemansetrecipients: + markroseman, terry.reedy, kbk, roger.serwy
2015-10-04 18:56:39markrosemansetmessageid: <1443984999.04.0.662978641564.issue25313@psf.upfronthosting.co.za>
2015-10-04 18:56:39markrosemanlinkissue25313 messages
2015-10-04 18:56:38markrosemancreate