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 Shane Smith
Recipients Shane Smith, paul.moore, steve.dower, terry.reedy, tim.golden, veky, zach.ware
Date 2017-01-11.16:53:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I'm fine with a single implementation, so long as the implementation is what's best for the majority of users.  Not my intent to increase the burden of work.

So, let me ask the question alluded to in my first post: when is a nested menu actually desirable?  I would argue that the vast majority of users have one or two versions of Python installed at any given time.  And for that number, a flat menu is certainly preferred.

The X.Y version numbering in the context menu introduced as a result of issue23546 solves said issue.  I'm merely suggesting de-nesting the menu.
Date User Action Args
2017-01-11 16:53:09Shane Smithsetrecipients: + Shane Smith, terry.reedy, paul.moore, tim.golden, zach.ware, steve.dower, veky
2017-01-11 16:53:09Shane Smithsetmessageid: <>
2017-01-11 16:53:09Shane Smithlinkissue27603 messages
2017-01-11 16:53:09Shane Smithcreate