On 17 July 2016 at 11:27, Ned Deily wrote:
> On Jul 16, 2016, at 20:46, Brett Cannon 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
More importantly, you'd get into lots of situations where the heads of the
two trees don't work together. And separate versioning is just not
realistic for the stdlib.
On Saturday, July 16, 2016, Oleg Broytman wrote:
> On Sun, Jul 17, 2016 at 10:59:57AM +1000, Chris Angelico > wrote:
> > Oh, an
I think Ned strikes the nail on the head. It's a fair burden to keep
the repos in sync. I propose that instead we have some script that can
make a release of just the stdlib for the benefits of other Python
implementations.
FWIW I've got a fair bit of experience using a subrepo for a similar
purpo
On Jul 16, 2016, at 20:46, Brett Cannon 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
On Sun, Jul 17, 2016 at 10:59:57AM +1000, Chris Angelico
wrote:
> Oh, and if you tell people to do it this way, you can "ln -s
> ../python-stdlib Lib" and commit that symlink into the repo.
Doesn't work on w32 AFAIK.
Oleg.
--
Oleg Broytmanhttp://phdru.name/p...@
On Sun, Jul 17, 2016 at 10:59 AM, Ryan Gonzalez wrote:
>> I detest working with git submodules; if the repositories get split,
>> I'd much rather have ./python look for ../python-stdlib as a parallel
>> repo. They stand entirely separately; you simply clone both repos into
>> the same directory. (
On Jul 16, 2016 7:54 PM, "Chris Angelico" wrote:
>
> On Sun, Jul 17, 2016 at 10:46 AM, Brett Cannon wrote:
> > For instance, would we be able to split the history, or would the
original
> > history stay in the CPython repo and we would start from scratch in the
> > stdlib repo and `git log` would
On Sun, Jul 17, 2016 at 10:54 AM, Chris Angelico wrote:
> if the repositories get split,
> I'd much rather have ./python look for ../python-stdlib as a parallel
> repo. They stand entirely separately; you simply clone both repos into
> the same directory.
Oh, and if you tell people to do it this
> On Jul 16, 2016, at 8:46 PM, Brett Cannon wrote:
>
> What would be involved in making the stdlib its own repo, separate from
> CPython itself? Now I'm not suggesting making sure it fully functions on its
> own, but more of what would need to happen if we decided that the stdlib
> should be
On Sun, Jul 17, 2016 at 10:46 AM, Brett Cannon wrote:
> For instance, would we be able to split the history, or would the original
> history stay in the CPython repo and we would start from scratch in the
> stdlib repo and `git log` would hopefully be smart enough to merge the two
> histories? How
What would be involved in making the stdlib its own repo, separate from
CPython itself? Now I'm not suggesting making sure it fully functions on
its own, but more of what would need to happen if we decided that the
stdlib should be its own git repo so that any Python implementation --
including CP
11 matches
Mail list logo
