[core-workflow] What would it take to split the stdlib out into its own git repo?

[Ned Deily]

On Jul 16, 2016, at 20:46, Brett Cannon <brett at python.org> wrote:
> And are there benefits? My hope/hunch is that if we make the stdlib its own repo then other implementations could include the stdlib as a submodule or something, making it easier for them to not only keep up-to-date with fixes to the stdlib, but also make it easier for them to push changes upstream that everyone would benefit from instead of having any changes silo-ed off in their own repo.

Without giving it a lot of thought, this strikes me as an unnecessary complication.  It will undoubtedly make CPython development more complicated, both initially in separating the stdlib out and, in the long run, figuring out how to keep them in sync all the time.  Other Python implementations already have to deal with this, if they want to, and they can very easily ignore the CPython-specific parts of the repo without having to add all this additional work on everyone.  Let's not make this migration harder than it has to be.  We've got enough to do already.

--
  Ned Deily
  nad at python.org -- []