Re: Closing out 2.7 beta 4
Jeff Hardy <[email protected]>
| Newsgroups | gmane.comp.lang.jython.devel |
|---|---|
| Message-ID | <CAF7AXFECk+j4zBN7XN3RsVE+HdEwDET6KB4GVPS-y5EEOnYg6w@mail.gmail.com> |
On Mon, Oct 13, 2014 at 10:10 PM, Jim Baker <[email protected]> wrote: > On Mon, Oct 13, 2014 at 2:36 PM, Pekka Klärck <[email protected]> wrote: >> >> ... >> >> If pip already works well, why is it going to be dropped from 2.7? > > > So we have two things: ensurepip, which gets the latest version of pip > installed; and pip itself. The ensurepip module is being backported to 2.7, > so it's possible we could still benefit from that, possibly in time for > 2.7.0. But I don't think it should hold up the 2.7.0 release either. > >> >> Would there be too much work bundling it in? Anything where others who >> could help? It would be so much easier for users if pip was included >> out-of-the-box, especially if the standard pip still wouldn't work. > > > It's just a triage decision. 2.7.0 trunk is highly usable as it is, so I do > not want to hold it up even for a great new feature like ensurepip. But we > can readily include ensurepip in 2.7.1. > > But a pull request, with testing, that adds in ensurepip - of course we > would merge that. IronPython has a version of ensurepip to be included in 2.7.5, if that's nay help at all. There aren't too many changes needed from the standard ensurepip. - Jeff ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ Jython-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jython-dev