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 zach.ware
Recipients loewis, paul.moore, steve.dower, tim.golden, zach.ware
Date 2015-04-09.13:06:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAKJDb-NP_z7-VY0BWiS5qgChCt2sGOn6B76Gi2CVu1Av7Jnc8A@mail.gmail.com>
In-reply-to <1428576631.18.0.453965054644.issue21411@psf.upfronthosting.co.za>
Content
Steve Dower added the comment:
> I think we should fix all the warnings, but turning this on is a great
way to make the build bots red often.

That is the obvious downside. On the other hand, we do have a very old open
issue (though I don't have the number handy) in which Guido made clear that
a build with no warnings on every possible platform would be ideal and is
desired, and this would help make sure we stay there when we reach that
point.

> I believe they already go yellow for warnings, so people are somewhat
informed, but I don't think we want to be more aggressive than that.

The individual step is colored yellow, but not the whole build. So if
you're just looking at the headings on the waterfall page, you'll never
notice. I'm not sure if we can change that setting, but that might be a
nicer solution.

> Also, I know someone who has a patch coming that fixes most of these, so
we can ignore this for a bit more and just get the fix that way if we want.

Ok, that sounds good. When that issue opens, would you mind linking it as a
dependency of this one?
History
Date User Action Args
2015-04-09 13:06:24zach.waresetrecipients: + zach.ware, loewis, paul.moore, tim.golden, steve.dower
2015-04-09 13:06:24zach.warelinkissue21411 messages
2015-04-09 13:06:23zach.warecreate