Showing content from http://mail.python.org/pipermail/python-dev/attachments/20130104/96b6c56a/attachment.html below:
<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div style="-webkit-text-size-adjust: auto; ">On Jan 4, 2013, at 10:23 AM, "R. David Murray" <<a href="mailto:rdmurray@bitdance.com">rdmurray@bitdance.com</a>> wrote:</div><div style="-webkit-text-size-adjust: auto; "><br></div><blockquote type="cite" style="-webkit-text-size-adjust: auto; "><div><span>On Fri, 04 Jan 2013 10:04:14 -0500, Todd V Rovito <<a href="mailto:rovitotv@gmail.com">rovitotv@gmail.com</a>> wrote:</span><br><blockquote type="cite"><span> I submitted a simple patch for updates to IDLE's documentation</span><br></blockquote><blockquote type="cite"><span> <a href="http://bugs.python.org/issue5066">http://bugs.python.org/issue5066</a> and it has not been reviewed by</span><br></blockquote><blockquote type="cite"><span> an official Python developer. Since it is now been over 1month</span><br></blockquote><blockquote type="cite"><span> since last update can somebody please review and or commit? I</span><br></blockquote><blockquote type="cite"><span> did get some comments from another contributor and updated the</span><br></blockquote><blockquote type="cite"><span> patch based on those comments. The original bug was opened in</span><br></blockquote><blockquote type="cite"><span> 2009 and the IDLE documentation is out of date with undocumented</span><br></blockquote><blockquote type="cite"><span> menu options and inconsistencies between the help file and the</span><br></blockquote><blockquote type="cite"><span> HTML documentation. I hate to be pushy but I would like to see</span><br></blockquote><blockquote type="cite"><span> some progress made on IDLE. Thanks for the support.</span><br></blockquote><span></span><br><span>IMO it isn't pushy to ask about an issue that seems ready but on which</span><br><span>no action has been taken for an extended period. It could be that the</span><br><span>nosy committers have just forgotten about it.</span><br><span></span><br><span>In the future, it best way to approach this situation (patch that seems</span><br><span>ready but no action has been taken) is to ping the issue first, and if</span><br><span>you don't get a response after a few days, to post here as you did.</span><br></div></blockquote><span style="-webkit-text-size-adjust: auto;">Good suggestion I will "ping" the bug report! FYI....the excellent developer's guide </span><span style="-webkit-text-size-adjust: none; font-size: 15px; line-height: 19px; white-space: nowrap; -webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); "><a href="http://docs.python.org/devguide/patch.html#reviewing">http://docs.python.org/devguide/patch.html#reviewing</a> states "</span><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">Getting your patch reviewed requires a reviewer to have the spare time and motivation to look at your patch (we cannot force anyone to review patches). If your patch has not received any notice from reviewers (i.e., no comment made) after a substantial amount of time then you may email <a class="reference external" href="mailto:python-dev%40python.org" style="text-decoration: none; ">python-dev@python.org</a> asking for someone to take a look at your patch."</span><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="-webkit-text-size-adjust: auto;">The Developer's guide does not mention pinging the patch maybe that is common sense so it doesn't need to be documented but I had assumed somebody was watching bugs that had patches applied but no commits. </span></div></body></html>
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