On 10 June 2013 06:43, Marcus Smith <span dir="ltr">&lt;<a href="mailto:qwcode@gmail.com" target="_blank">qwcode@gmail.com</a>&gt;</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">
maybe this was covered before, but I&#39;m looking for clarification on how pip upgrades are to work under PEP439.<div><br></div><div>I see 3 relevant bits right now:</div><div><br></div><div><div>1) &quot;attempts to import pip machinery. If it can then the pip command proceeds as normal&quot;</div>

<div><br></div><div>i.e., once it has a pip installed, it doesn&#39;t automatically upgrade on subsequent imports.</div></div></blockquote><div><br></div><div>That&#39;s the intention. I&#39;ve modified that paragraph:</div>
<div><br></div><div>&quot;&quot;&quot;</div><div>The Python installation includes an executable called &quot;pip3&quot; (see PEP 394 for</div><div>naming rationale etc.) that attempts to import pip machinery.  If it can then</div>
<div>the pip command proceeds as normal.  If it cannot it will bootstrap pip by</div><div>downloading the pip implementation wheel file.  Once installed, the pip</div><div>command proceeds as normal. Once the bootstrap process is complete the &quot;pip3&quot;</div>
<div>command is no longer the bootstrap but rather the full pip command.</div><div>&quot;&quot;&quot;</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>2) &quot;A bootstrap is used in the place of a the full pip code so that we don&#39;t have to bundle pip and also the install tool is upgradeable outside of the regular Python upgrade timeframe and processes&quot;</div>

<div><br></div><div>to be clear, what is the &quot;install tool&quot; here?  pip? or the bootstrap?</div></blockquote><div><br></div><div>I will edit the PEP to replace &quot;install tool&quot; with &quot;pip&quot;:</div>
<div><br></div><div>&quot;&quot;&quot;</div><div><div>A boostrap is used in the place of a the full pip code so that we don&#39;t have</div><div>to bundle pip and also pip is upgradeable outside of the regular Python</div>
<div>upgrade timeframe and processes.</div></div><div>&quot;&quot;&quot;</div><div> </div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>3) &quot;Manual installation of the pip implementation will be supported through the manual download of the wheel file and &quot;pip3 install &lt;downloaded wheel file&gt;. This installation will not perform standard pip installation steps of saving the file to a cache directory or updating any local database of installed files.&quot;&quot;</div>

<div><br></div><div>I guess this means &quot;manual upgrades&quot; as well?</div><div>this special logic is to be inside pip itself? or an override of &quot;install&quot; in the bootstrap (that detects when it&#39;s a pip wheel)?</div>
</blockquote><div><br></div><div>I&#39;ve modified this section to read:</div><div><br></div><div>&quot;&quot;&quot;</div><div><div>Some users may have no Internet access suitable for fetching the pip</div><div>implementation file. Manual installation of the pip implementation will be</div>
<div>supported through the manual download of the wheel file and &quot;pip3 install</div><div>&lt;downloaded wheel file&gt;&quot;. This installation - since it uses only the bootstrap</div><div>code - will not perform standard pip installation steps of saving the file to</div>
<div>a cache directory or updating any local database of installed files.</div></div><div>&quot;&quot;&quot;</div><div><br></div><div>These changes will be online soon.</div><div><br></div><div><br></div><div>     Richard</div>
<div><br></div></div>