Greg Ewing <greg@cosc.canterbury.ac.nz> writes: > > It means that your code *will* break in Python 2.4, unless you take > > corrective action (which you cannot take at the moment). > > Pardon me, but... wouldn't it have been better to defer > introducing these warnings until there *is* something > that can be done about them? That might be the case. At the time the warning was added, there was consensus that it is be easy to do something about each of them. It was only detected later that it is not easy in some cases (strictly speaking, you can correct all the warnings today, taking, for example, the approach that Jack would take, of adding a custom conversion function into your C modules). Today, I would rather hope that somebody contributes a patch to add the requested features instead of contributing a patch to disable the warning. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4