Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Issue #7849: Now the utility ``check_warnings`` verifies if the warnings are | Florent Xicluna | 2010-03-07 | 1 | -4/+1 |
| | | | | effectively raised. A new utility ``check_py3k_warnings`` deals with py3k warnings. | ||||
* | DeprecationWarning is now silent by default. | Brett Cannon | 2010-01-10 | 1 | -0/+2 |
| | | | | | | | | | | | | This was originally suggested by Guido, discussed on the stdlib-sig mailing list, and given the OK by Guido directly to me. What this change essentially means is that Python has taken a policy of silencing warnings that are only of interest to developers by default. This should prevent users from seeing warnings which are triggered by an application being run against a new interpreter before the app developer has a chance to update their code. Closes issue #7319. Thanks to Antoine Pitrou, Ezio Melotti, and Brian Curtin for helping with the issue. | ||||
* | Improved test for a deprecation warning. | Eric Smith | 2009-10-31 | 1 | -2/+1 |
| | |||||
* | Issue #5835, deprecate PyOS_ascii_formatd. | Eric Smith | 2009-04-25 | 1 | -0/+62 |
If anyone wants to clean up the documentation, feel free. It's my first documentation foray, and it's not that great. Will port to py3k with a different strategy. |