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 brett.cannon, jcea, kidanger, loewis, poolie, python-dev, terry.reedy, vstinner
Date 2012-08-19.19:25:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1345404342.61.0.60553703235.issue10951@psf.upfronthosting.co.za>
In-reply-to
Content
(As usual), I'm quite skeptical about this "bulk bug report"; it violates the "one bug at a time" principle, where "one bug" can roughly be defined as "cannot be split into smaller independent issues".

For the cases at hand, I think it would be best if somebody with gcc 4.6 available just fixed the "easy" ones, i.e. where the code clearly improves when silenciing the warning. In these cases, I wouldn't mind if they get checked in without code review; I know some favor review for all changes, in which case a separate issue should be opened for a patch fixing a bunch of these.

The more difficult ones may deserve their own issues (e.g. when it is debatable whether gcc is right to warn about the code)
History
Date User Action Args
2012-08-19 19:25:42loewissetrecipients: + loewis, brett.cannon, terry.reedy, jcea, vstinner, python-dev, poolie, kidanger
2012-08-19 19:25:42loewissetmessageid: <1345404342.61.0.60553703235.issue10951@psf.upfronthosting.co.za>
2012-08-19 19:25:21loewislinkissue10951 messages
2012-08-19 19:25:21loewiscreate