Martin v. Löwis added the comment:

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.

----------
nosy: +loewis

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25878>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to