Showing content from http://mail.python.org/pipermail/python-dev/attachments/20100415/7ed7af9e/attachment.html below:
<p>Yes, we have different opinions. My personal take is to wait a week before you email python-dev if there has been no activity. That is enough time for people interested in the patch to get to it as we all have different schedules. Any faster and it feels like noise on the list to me.</p>
<p>Brett (from his phone)</p>
<p>On Apr 14, 2010 11:28 PM, "Glyph Lefkowitz" <<a href="mailto:glyph@twistedmatrix.com">glyph@twistedmatrix.com</a>> wrote:<br></p>
<p><font color="#500050">On Apr 14, 2010, at 5:19 PM, Brett Cannon wrote:</font></p>
<p><font color="#500050">> I see the confusion. I think Martin meant more about open issues that required discussion, not sim...</font></p>
<p>Ach. Â I hit 'send' too soon. Â I also wanted to say: it seemed quite clear to me that Martin specifically meant "simply issues that had a patch ready to go". Â Quoting him exactly:</p>
<p><blockquote type="cite"><span style="font-family:Times"><pre></pre></span></blockquote><blockquote type="cite"><div><blockquote type="cite"><span style="font-family:Times"><pre>Please understand that setting the state of an issue to "review" may *not* be the best way to trigger a review - it may be more effective to post to python-dev if you truly believe that the patch can be committed as-is.</pre>
</span></blockquote></div></blockquote><div>It seems that perhaps the core developers have slightly different opinions about this? :)</div><div><br></div></p>
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