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 loewis
Recipients Arfrever, alex, certik, dmalcolm, loewis, ncoghlan, pitrou, skrah, teoliphant, vstinner
Date 2012-08-03.09:18:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <20120803111807.Horde.IHjPH6GZi1VQG5dPtLawPpA@webmail.df.eu>
In-reply-to <1343953134.27.0.983729668691.issue15540@psf.upfronthosting.co.za>
Content
> FWIW, with regard to Martin's tangential comment about appropriate  
> use of the tracker, I'm personally fine with using the tracker for  
> 'I found this problem, attempted to fix it (but failed), here's my  
> attempt'.

I don't mind that at all, either. What I dislike is "I have this issue,
here is what I've got, and I will continue to work on it" kind of reports
(when Dave clearly said that his patch is work-in-progress). There is a
worse kind, where people say "I have this issue", followed (after 15 minutes)
with "I found out more", and then going on with that for a while. I feel
that this wastes the reader's time (who may actually start to work on the
issue as well, duplicating efforts) - this is something that submitters
really need to consider. It's not this bad in this issue, since Dave said
from the beginning that it is work-in-progress.

On-topic: what action do you suggest for this issue?
History
Date User Action Args
2012-08-03 09:18:10loewissetrecipients: + loewis, teoliphant, ncoghlan, pitrou, vstinner, Arfrever, certik, alex, skrah, dmalcolm
2012-08-03 09:18:09loewislinkissue15540 messages
2012-08-03 09:18:08loewiscreate