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 terry.reedy
Recipients dstufft, lorenzogotuned, ncoghlan, ned.deily, terry.reedy, upendra-k14
Date 2016-06-21.22:39:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1466548744.63.0.788788812798.issue27051@psf.upfronthosting.co.za>
In-reply-to
Content
I rechecked #23351 and in msg249924 Donald did disclaim any guarantee that using main() would work forever.  He suggested instead using subprocess and the command line interface as presumably more stable.

In tem_pip_v3.py Upendra switched to using subprocess and I presume he stuck with that in spite of any suggestion otherwise from me.  If the pip command line interface is changed, *every* program that uses it could be broken.

I agree with Ned that pip_gui should ideally be part of the pip package, I would be happy if Donald were to review what Upendra has and will produce, pronounce it good, and ask to have it for pip.
History
Date User Action Args
2016-06-21 22:39:04terry.reedysetrecipients: + terry.reedy, ncoghlan, ned.deily, dstufft, upendra-k14, lorenzogotuned
2016-06-21 22:39:04terry.reedysetmessageid: <1466548744.63.0.788788812798.issue27051@psf.upfronthosting.co.za>
2016-06-21 22:39:04terry.reedylinkissue27051 messages
2016-06-21 22:39:04terry.reedycreate