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.

M

--
Matt Billenstein
m...@vazor.com

Sent from my iPhone 6 (this put here so you know I have one)

> On Mar 24, 2018, at 8:27 PM, Nick Coghlan <ncogh...@gmail.com> wrote:
> 
>> On 25 March 2018 at 06:52, Ned Deily <n...@python.org> wrote:
>> On Mar 24, 2018, at 16:13, Steve Dower <steve.do...@python.org> wrote:
>> > 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.)
>> 
>> 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.
> 
> 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.
> 
> 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.
> 
> Cheers,
> Nick.
> 
> -- 
> Nick Coghlan   |   ncogh...@gmail.com   |   Brisbane, Australia
> _______________________________________________
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: 
> https://mail.python.org/mailman/options/python-dev/matt%40vazor.com
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Reply via email to