<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jul 18, 2013, at 2:45 AM, Paul Moore <<a href="mailto:p.f.moore@gmail.com">p.f.moore@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div class="gmail_extra">On 18 July 2013 02:03, Donald Stufft <span dir="ltr"><<a href="mailto:donald@stufft.io" target="_blank">donald@stufft.io</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div id=":284" style="overflow:hidden">it's simple to upgrade the pip if the user requires a newer version<br>
of pip using ``pip install --upgrade pip`</div></blockquote></div><br>Please don't gloss over the potential issues with upgrading in the face of in-use exe wrappers. We have a design for a solution, but as yet no working code. I expect to work on this, but my time is limited and I'm not at all sure there won't be issues still to resolve. (Obviously, anyone else is welcome to help, but it's a "windows issue", so I don't know how much interest there will be from non-Windows developers).</div></div></blockquote><div><br></div><div>That's a bug ;) And will be worked around one way or another even if I need to install Windows to make it happen in time.</div><br><blockquote type="cite"><div dir="ltr">
<div class="gmail_extra"><br></div><div class="gmail_extra">Prior to the setuptools move away from 2to3, my standard response to anyone reporting issues with in-place upgrades of setuptools or pip (certainly on Windows, and in general anywhere else too) was "well, don't do that - remove and reinstall manually". Things are better now, but not yet perfect and I don't believe that there is a consensus that this is acceptable for a bundled pip.</div></div></blockquote><div><br></div><div>I consider "remove and reinstall" to be a terrible UX and if that's the best answer pip can give we need to fix that regardless. But as I said I don't mind ``python -mgetpip`` existing for one reason or another. I just don't think a bootstrap command is our best option for providing the most streamlined user experience.</div><div><br></div><div>Either way running an old pip is hardly that big of a deal. Anyone using a Linux distro is likely to be running an older version unless they've gone out of their way to upgrade it.</div></div><div apple-content-edited="true"><br>-----------------<br>Donald Stufft<br>PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
</div>
<br></body></html>