On Sun, Jun 10, 2012 at 12:05 PM, Brett Cannon <br...@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 | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
