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, terry.reedy, upendra-k14
Date 2016-06-22.01:00:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1466557208.87.0.0832026217078.issue27051@psf.upfronthosting.co.za>
In-reply-to
Content
pip_gui.pip_tkinter.utils.runpip has indeed switched to using subprocess (and yes, the PyPA crew are significantly more careful with backwards compatibility there), but there are still a couple of other API imports in that module: https://github.com/upendra-k14/pip_gui/blob/dump_code/pip_tkinter/utils.py#L7 (I didn't check other code to see if the affected APIs are used anywhere)

I do like the idea of *bundling* pip_gui in a variant of the ensurepip style, rather than having it as a conventional standard library component, though - it means we can simplify the backwards compatibility guarantee by noting that, if you're using the provided GUI, doing "pip install --upgrade pip" may also require doing "pip install --upgrade pip-tkinter".
History
Date User Action Args
2016-06-22 01:00:09ncoghlansetrecipients: + ncoghlan, terry.reedy, ned.deily, dstufft, upendra-k14, lorenzogotuned
2016-06-22 01:00:08ncoghlansetmessageid: <1466557208.87.0.0832026217078.issue27051@psf.upfronthosting.co.za>
2016-06-22 01:00:08ncoghlanlinkissue27051 messages
2016-06-22 01:00:07ncoghlancreate