Guido van Rossum wrote:
> Suggestion for people asking developers to look into issues: indicate
> more than the issue number in the email. Show the issue summary, other
> relevant metadata, and what needs to be done in some detail. This will
> pique the interest of those who *can* help (and allow people who can't
> help anyway to skip the message more efficiently).
Links of the form http://bugs.python.org/issue2944 don't hurt either :)
That particular issue is an asyncore problem, so I cc'ed Josiah directly
on this message.
Cheers,
Nick.
>
> On Thu, Jul 17, 2008 at 12:41 PM, Alexander Shigin <shigin at rambler-co.ru> wrote:
>> Can anyone look at the patch for Issue2944?
>>
>> I hope the issue can be fixed before the release of python 2.6.
>
--
Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
---------------------------------------------------------------
http://www.boredomandlaziness.org
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