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 | bethard |
|---|---|
| Recipients | benjamin.peterson, bethard |
| Date | 2008年03月18日.21:15:11 |
| SpamBayes Score | 0.11330184 |
| Marked as misclassified | No |
| Message-id | <1205874912.34.0.0448524738909.issue2402@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Fair enough. I agree that the deprecated APIs should still be tested. But there are a lot of other warnings, e.g. where the standard lib uses ``has_key`` instead of ``in``. These should be removed. The only warnings should be those that are actively testing deprecated APIs. Testing of deprecated APIs should probably temporarily suppress the Py3K warnings while they're executing, though that's not really crucial. Reducing the flood of warnings is really worthwhile -- I just fixed a bug in test_atexit which only appeared when -3 was supplied. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年03月18日 21:15:12 | bethard | set | spambayes_score: 0.113302 -> 0.11330184 recipients: + bethard, benjamin.peterson |
| 2008年03月18日 21:15:12 | bethard | set | spambayes_score: 0.113302 -> 0.113302 messageid: <1205874912.34.0.0448524738909.issue2402@psf.upfronthosting.co.za> |
| 2008年03月18日 21:15:11 | bethard | link | issue2402 messages |
| 2008年03月18日 21:15:11 | bethard | create | |