Home Original page

[Python-Dev] release cadence

Nick Coghlan ncoghlan at gmail.com
Tue Jul 5 21:07:52 EDT 2016 
On 6 July 2016 at 03:47, Barry Warsaw <barry at python.org> wrote:
> On Jul 05, 2016, at 10:38 AM, Steve Dower wrote:
>
>>My hope is that it would be essentially a "pip freeze"/"pip install -r ..."
>>(or equivalent with whatever tool is used/created for managing the
>>stdlib). Perhaps using VCS URIs rather than version numbers?
>>
>>That is, the test run would dump a list of exactly which stdlib versions it's
>>using, so that when you review the results it is possible to recreate it.
>
> I think you'd have to have vcs checkouts though, because you will often need
> to fix or change something in one of those other library pieces.  The other
> complication of course is that now you'll have two dependent PRs with reviews
> in two different repos.

I'd actually advocate for keeping a unified clone, and make any use of
pip to manage pieces of the standard library purely an install-time
thing (as it is for ensurepip).

The main problem I see with actually making stdlib development
dependent on having a venv already set up for pip to do its thing
without affecting the rest of your system is that it would pose a
major bootstrapping problem.

It does mean we'd be introducing a greater divergence between the way
devs work locally and the way the CI system worked (as in this model
we'd definitely want the buildbots to be exercising both the "test in
checkout" and "test an installed version" case), but working across
multiple repos would be worse.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
More information about the Python-Dev mailing list