This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients BreamoreBoy, benjamin.peterson, christian.heimes, terry.reedy, vstinner
Date 2014-10-05.21:20:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwbYmPSQKzdWe_PDR-mwduMDXnvTcM=hjOJRCiTNQhdBXQ@mail.gmail.com>
In-reply-to <1412532283.98.0.195460698999.issue18372@psf.upfronthosting.co.za>
Content
Le 5 oct. 2014 20:04, "Mark Lawrence" <report@bugs.python.org> a écrit :
>
>
> Mark Lawrence added the comment:
>
> @Christian/Victor could either of you provide a patch for this, it's way
beyond my knowledge I'm afraid.

I agree with Benjamin. Asking directly two developers to write a patch
don't add any value to the issue, it only puts pressure on them. If I
didn't write a patch before, it's probably because I'm not really
interested by the topic.

If you would like to contribute, you can close directly issues, test and
review patches, suggest an implementation, etc.

It's not all black or all white. Sometimes, your "ping" messages are
helpful reminders to finish the work or simply to close the issue.

By experience, most old issues are not finished because the bug only impact
a few people and it's possible to work around it, or because the feature
request is not interesting enough.

I didn't read this issue (i'm replying in my mail client), my remarks are
general.
History
Date User Action Args
2014-10-05 21:20:23vstinnersetrecipients: + vstinner, terry.reedy, christian.heimes, benjamin.peterson, BreamoreBoy
2014-10-05 21:20:23vstinnerlinkissue18372 messages
2014-10-05 21:20:22vstinnercreate