<br><br><div class="gmail_quote">On Mon, Jun 11, 2012 at 12:39 PM, Barry Warsaw <span dir="ltr">&lt;<a href="mailto:barry@python.org" target="_blank">barry@python.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<div class="im">On Jun 11, 2012, at 04:58 PM, Nick Coghlan wrote:<br>
<br>
&gt;1. Asking on python-dev is considered adequate. If an implementation<br>
&gt;wants to be consulted on changes, one or more of their developers<br>
&gt;*must* follow python-dev sufficiently closely that they don&#39;t miss<br>
&gt;cross-VM compatibility questions.<br>
<br>
</div>That&#39;s certainly my preference.<br></blockquote><div><br></div><div>Right, because it&#39;s easiest for you and everyone else who follows python-dev already. =) But that doesn&#39;t improve the situation; those of us who have needed to chat with the other VMs know the status quo is not an optimal (or even decent) solution. I only pull anything off because I know someone on every VM team and so I have email addresses and names. But that shouldn&#39;t be a private email conversation, nor should it require that much effort, especially if it requires pulling in someone from some other VM team that I either don&#39;t know or didn&#39;t have a clue should be included in the conversation.</div>

<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
&gt;(My concern is that this isn&#39;t<br>
&gt;reliable - we know from experience that other VMs can miss such<br>
&gt;questions when they&#39;re mixed in with the rest of the python-dev<br>
&gt;traffic)<br>
&gt;<br>
&gt;2. As 1, but we adopt a subject line convention to make it easier to<br>
&gt;filter out general python-dev traffic for those that are just<br>
&gt;interested in cross-vm questions<br>
<br>
</div>+1<br></blockquote><div><br></div><div>But that then requires new people to the list learn about this &quot;magical&quot; convention. We already know people don&#39;t always read the intro paragraph to the mailing list to say this is for development *of* Python, why do you think this will be any better? The anti-top-posting happens only because everyone replies inline so people just naturally follow that. I don&#39;t see people remembering to use the magical subject line consistently. This would also be the first time one has to set up a special email filtering rule for python-dev to get a result that people are expected to have available to them.</div>

<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
&gt;As Brett pointed out, it&#39;s similar to the resurrection of import-sig -<br>
&gt;we know that decisions aren&#39;t final until they&#39;re resolved on<br>
&gt;python-dev, but it also means we&#39;re not flooding python-dev with<br>
&gt;interminable arcane discussions on import system internals.<br>
<br>
</div>I personally already ignore much of python-dev and only chime in on subjects I<br>
both care about and delude myself into thinking I have something useful to<br>
contribute. For cases where I miss something and need to catch up, Gmane is<br>
perfect.<br></blockquote><div><br></div><div>But your search area of interest is probably quite larger than that for other VM implementers. Being into VMs and compatibility &lt;&gt; into language design which the bulk of python-dev is about (and yes, I used that not-equals operator just for you, Barry, to get the point across =).</div>

</div>

AltStyle によって変換されたページ (->オリジナル) /