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 ned.deily
Recipients lorenzogotuned, ncoghlan, ned.deily, terry.reedy, upendra-k14
Date 2016-06-21.02:14:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1466475282.93.0.113295127518.issue27051@psf.upfronthosting.co.za>
In-reply-to
Content
One other possibility: decouple the gui from both Python and pip releases by packaging and, at least initially, releasing it through PyPI as an independent project.  That is, after all, the preferred mechanism for adding new functionality to the standard library.  The only thing that would need to be in the standard library then is an IDLE version of "ensuregui", serving the same purpose as "ensurepip", to provide an easy way for IDLE users to initially install the gui using pip and PyPI.  If, down the road, the gui is a success and the long-term support issues can be addressed, bringing the gui directly under the pip project could happen in the future.
History
Date User Action Args
2016-06-21 02:14:42ned.deilysetrecipients: + ned.deily, terry.reedy, ncoghlan, upendra-k14, lorenzogotuned
2016-06-21 02:14:42ned.deilysetmessageid: <1466475282.93.0.113295127518.issue27051@psf.upfronthosting.co.za>
2016-06-21 02:14:42ned.deilylinkissue27051 messages
2016-06-21 02:14:42ned.deilycreate