RetroSearch Browse

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/attachments/20120610/33d8db02/attachment.html below:

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.

<div class="gmail_quote">On Jun 10, 2012 8:42 PM, "Guido van Rossum" <<a href="mailto:guido@python.org">guido@python.org</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

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 <<a href="mailto:ncoghlan@gmail.com">ncoghlan@gmail.com</a>> wrote: 
> On Sun, Jun 10, 2012 at 12:05 PM, Brett Cannon <<a href="mailto:brett@yvrsfo.ca">brett@yvrsfo.ca</a>> 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Â Â |Â Â <a href="mailto:ncoghlan@gmail.com">ncoghlan@gmail.com</a>Â Â |Â Â Brisbane, Australia 
> _______________________________________________ 
> Python-Dev mailing list 
> <a href="mailto:Python-Dev@python.org">Python-Dev@python.org</a> 
> <a href="http://mail.python.org/mailman/listinfo/python-dev" target="_blank">http://mail.python.org/mailman/listinfo/python-dev</a> 
> Unsubscribe: <a href="http://mail.python.org/mailman/options/python-dev/guido%40python.org" target="_blank">http://mail.python.org/mailman/options/python-dev/guido%40python.org</a> 
 
 
 
-- 
--Guido van Rossum (<a href="http://python.org/~guido" target="_blank">python.org/~guido</a>) 
</blockquote></div>

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4