[Python-Dev] backporting stdlib 2.7.x from pypy to cpython

[Guido van Rossum]

But what guarantee do you have that (a) the right people sign up for
the new list, and (b) topics are correctly brought up there instead of
on python-dev? I agree that python-dev is turning into a firehose, but
I am reluctant to create backwaters where people might arrive at what
they think is a consensus only because the important opinions aren't
represented there.

On Sun, Jun 10, 2012 at 6:10 PM, Brett Cannon <brett at yvrsfo.ca> wrote:
> I am proposing a single list to just discuss multi-vm issues so that it
> doesn't force all other VM contributors to sign up for python-dev if they
> don't care about language issues. We could hijack the stdlib-sig mailing
> list, but that isn't the right focus necessarily.
>
> On Jun 10, 2012 8:42 PM, "Guido van Rossum" <guido at python.org> wrote:
>>
>> Really? Are we now proposing multiple lists? That just makes it easier
>> to miss stuff for me.
>>
>> On Sun, Jun 10, 2012 at 5:53 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:
>> > On Sun, Jun 10, 2012 at 12:05 PM, Brett Cannon <brett at yvrsfo.ca> wrote:
>> >>> Well, the question is, are many python-dev discussions
>> >>> CPython(specific?
>> >>> If not, then it doesn't make a lot of sense to create
>> >>> python-implementations
>> >>> (and it's one more subscription to manage for those of us who want to
>> >>> keep
>> >>> an eye on all core development-related discussions).
>> >>>
>> >>
>> >> But the other VMs don't necessarily care about the development of the
>> >> language, so when the occasional thing comes up regarding all the VMs,
>> >> should that require they follow python-dev in its entirety? And I don't
>> >> see
>> >> the list making sweeping decisions that would affect CPython and
>> >> python-dev
>> >> without bringing it up there later. Think of the proposed list more
>> >> like a
>> >> SIG than anything else.
>> >
>> > Yeah, I think it makes sense. With the current situation, the bridges
>> > between the implementations are limited to those with the personal
>> > bandwidth to follow their implementation's core list *and* python-dev.
>> > With a separate list, it becomes easier to get feedback on cases where
>> > we want to check that an idea we're considering is feasible for all
>> > the major implementations.
>> >
>> > It also creates a neutral space for the other VMs to discuss stuff
>> > like collaborating on pure Python versions of C implemented modules.
>> > If we can get to the point where there's a separate "stdlib-only" pure
>> > Python mirror based on CPython's Mercurial repo that other
>> > implementations can all share, *without* requiring changes to CPython
>> > itself, that would be pretty nice.
>> >
>> > Cheers,
>> > Nick.
>> >
>> > --
>> > Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
>> > _______________________________________________
>> > Python-Dev mailing list
>> > Python-Dev at python.org
>> > http://mail.python.org/mailman/listinfo/python-dev
>> > Unsubscribe:
>> > http://mail.python.org/mailman/options/python-dev/guido%40python.org
>>
>>
>>
>> --
>> --Guido van Rossum (python.org/~guido)



-- 
--Guido van Rossum (python.org/~guido)