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 ncoghlan
Recipients dstufft, lorenzogotuned, ncoghlan, ned.deily, rhettinger, terry.reedy, upendra-k14
Date 2016-06-25.23:44:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1466898246.98.0.864990890773.issue27051@psf.upfronthosting.co.za>
In-reply-to
Content
Right, I think we need to separate two questions here:

1. Making a GUI for pip available *at all*. At the moment, there isn't really one, so even if instructors want to offer one, they can't without writing it first. That's a reported PyPA issue here: https://github.com/pypa/packaging-problems/issues/57

2. Whether to endorse and bundle such a GUI with CPython, and integrate it with IDLE.

I think the first aspect is an unequivocally good idea, and I'd encourage Upendra to head down that path to make it available to folks that are interested in having a cross-platform GUI for working with pip packages, regardless of what happens on the CPython integration front.

For the second point, I'll note that Donald was a trusted *PyPA* developer prior to our collaboration on PEP 453 - he became a CPython core developer specifically to maintain ensurepip.

I believe that "cross-community collaboration" model would also be a good fit for integration of a pip GUI distributed that was otherwise distributed via PyPI - we'd want core developers, or folks trusted by core developers, reviewing and maintaining the PyPI package, without necessarily pulling it directly into the CPython maintenance workflows.
History
Date User Action Args
2016-06-25 23:44:07ncoghlansetrecipients: + ncoghlan, rhettinger, terry.reedy, ned.deily, dstufft, upendra-k14, lorenzogotuned
2016-06-25 23:44:06ncoghlansetmessageid: <1466898246.98.0.864990890773.issue27051@psf.upfronthosting.co.za>
2016-06-25 23:44:06ncoghlanlinkissue27051 messages
2016-06-25 23:44:06ncoghlancreate