Showing content from http://mail.python.org/pipermail/python-dev/attachments/20180325/2913ce64/attachment.html below:
<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>As i recall git LFS makes storing large binary objects in some external object storage fairly seamless - might be a good fit for keeping the same workflow and not bloating the repo.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">M<br><br>--<div>Matt Billenstein</div><div><a href="mailto:matt@vazor.com">matt@vazor.com</a></div><div><br></div><div>Sent from my iPhone 6 (this put here so you know I have one)</div></div><div><br>On Mar 24, 2018, at 8:27 PM, Nick Coghlan <<a href="mailto:ncoghlan@gmail.com">ncoghlan@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 25 March 2018 at 06:52, Ned Deily <span dir="ltr"><<a href="mailto:nad@python.org" target="_blank">nad@python.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Mar 24, 2018, at 16:13, Steve Dower <<a href="mailto:steve.dower@python.org">steve.dower@python.org</a>> wrote:<br>
> Or we could just pull the right version directly from PyPI? (Note that updating the version should be an explicit step, as it is today, but the file should be identical to whatâs on PyPI, right? And a urlretrieve is easier than pulling from a git repo.)<br>
<br>
</span>I think the primary original rationale for having the pip wheel and its dependencies checked into the cpython repo was so that users would be able to install pip even if they did not have an Internet connection. But perhaps that requirement can be relaxed a bit if we say that the necessary wheels are vendored into all of our downloadable release items, that is, included in the packaging of source release files (the various tarballs) and the Windows and macOS binary installers. The main change would likely be making ensurepip a bit smarter to download if the bundled wheels are not present in the source directory. Assuming that people building from a cpython repo need to have a network connection if they want to run ensurepip, at least for the first time, is probably not an onerous requirement.<br></blockquote><div><br></div><div>Right, having the wheels in the release artifacts is a requirement, as is having them available for use when running the test suite, but having them in the git repo isn't.<br><br>Adding them directly to the repo was just the simplest approach to getting ensurepip working, since it didn't require any changes to the build process.<br></div><div><br></div><div>Cheers,<br></div><div>Nick.<br><br></div></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Nick Coghlan | <a href="mailto:ncoghlan@gmail.com" target="_blank">ncoghlan@gmail.com</a> | Brisbane, Australia</div>
</div></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Python-Dev mailing list</span><br><span><a href="mailto:Python-Dev@python.org">Python-Dev@python.org</a></span><br><span><a href="https://mail.python.org/mailman/listinfo/python-dev">https://mail.python.org/mailman/listinfo/python-dev</a></span><br><span>Unsubscribe: <a href="https://mail.python.org/mailman/options/python-dev/matt%40vazor.com">https://mail.python.org/mailman/options/python-dev/matt%40vazor.com</a></span><br></div></blockquote></body></html>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4