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 bruno.dupuis
Recipients bruno.dupuis, jcea
Date 2012-12-01.10:14:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1354356842.89.0.607858459151.issue16588@psf.upfronthosting.co.za>
In-reply-to
Content
I don't agree. Trash build logs are bad, trash code (I mean, in terms of utility, not quality :-) ) is far worst IMHO.

The purpose of this bug, to me, is to try to find a neat way to suppress the warnings without touching the code, and if we can't, wich is probable, we just tell the world : "Yeah, we know this bug, it's not ours and it has no inpact".

Anyway, I do not know the official policy for this kind of problem, but I really think we should avoid adding dead code as a workaround for every bug of every supported version of each supported compiler.
History
Date User Action Args
2012-12-01 10:14:02bruno.dupuissetrecipients: + bruno.dupuis, jcea
2012-12-01 10:14:02bruno.dupuissetmessageid: <1354356842.89.0.607858459151.issue16588@psf.upfronthosting.co.za>
2012-12-01 10:14:02bruno.dupuislinkissue16588 messages
2012-12-01 10:14:02bruno.dupuiscreate