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 Alexander Riccio, loewis, paul.moore, steve.dower, tim.golden, zach.ware
Date 2015-12-16.10:10:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The problem with this bug report is that there is little chance that it gets resolved in the near term, and it's quite possible that it will stay open for years. Somebody would have to sit down and start producing patches to fix these warnings correctly, before the actual patch can be applied.

I suggest not to add actual fixes to this issue, but instead create new issues that come with patches at creation, and that each fix a bunch of the warnings (either by warning type, or by code module). These issues could then be added as dependencies of this one. Otherwise, it will be difficult to track what precisely needs to be done on this issue.
Date User Action Args
2015-12-16 10:10:07loewissetrecipients: + loewis, paul.moore, tim.golden, zach.ware, steve.dower, Alexander Riccio
2015-12-16 10:10:07loewissetmessageid: <>
2015-12-16 10:10:07loewislinkissue25878 messages
2015-12-16 10:10:06loewiscreate