➜

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.

作者 ncoghlan
收信人 gvanrossum, ncoghlan, yselivanov
日期 2015-05-21.03:55:47
SpamBayes Score -1.0
Marked as misclassified 是
Message-id <1432180548.04.0.989622161613.issue24237@psf.upfronthosting.co.za>
In-reply-to
内容
Given the two-release deprecation cycle, would it be worth using PendingDeprecationWarning here? That way folks that only turned on DeprecationWarning (rather than -Wall) wouldn't need to worry about this until 3.6.

As far as our own test suite goes, when ResourceWarning was introduced, dealing with those in the test suite became an ongoing cleanup task. Are there really all that many warnings triggered for PEP 479?
历史
日期 用户 动作 参数
2015-05-21 03:55:48ncoghlan修改recipients: + ncoghlan, gvanrossum, yselivanov
2015-05-21 03:55:48ncoghlan修改messageid: <1432180548.04.0.989622161613.issue24237@psf.upfronthosting.co.za>
2015-05-21 03:55:48ncoghlan链接issue24237 messages
2015-05-21 03:55:47ncoghlan创建