| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | warnings.warn_explicit() did not have the proper TypeErrors in place to prevent | Brett Cannon | 2008-06-27 | 1 | -5/+13 | 
| | | | | | | | | | bus errors or SystemError being raised. As a side effect of fixing this, a bad DECREF that could be triggered when 'message' and 'category' were both None was fixed. Closes issue 3211. Thanks JP Calderone for the bug report. | ||||
| * | This reverts r63675 based on the discussion in this thread: | Gregory P. Smith | 2008-06-09 | 1 | -28/+28 | 
| | | | | | | | | http://mail.python.org/pipermail/python-dev/2008-June/079988.html Python 2.6 should stick with PyString_* in its codebase. The PyBytes_* names in the spirit of 3.0 are available via a #define only. See the email thread. | ||||
| * | turn PyErr_WarnPy3k into a macro | Benjamin Peterson | 2008-05-26 | 1 | -9/+0 | 
| | | |||||
| * | Renamed PyString to PyBytes | Christian Heimes | 2008-05-26 | 1 | -28/+28 | 
| | | |||||
| * | Fix a refleak in the _warnings module. | Georg Brandl | 2008-05-13 | 1 | -1/+3 | 
| | | |||||
| * | Fix logic error in Python/_warnings.c and add a test to verify | Benjamin Peterson | 2008-05-06 | 1 | -0/+2 | 
| | | |||||
| * | Fix a bug in the handling of the stacklevel argument in warnings.warn() where | Brett Cannon | 2008-05-06 | 1 | -3/+1 | 
| | | | | | the stack was being unwound by two levels instead of one each time. | ||||
| * | Add a DeprecationWarning for when warnings.showwarning() is set to a function | Brett Cannon | 2008-05-05 | 1 | -13/+43 | 
| | | | | | that lacks support for the new 'line' argument. | ||||
| * | Fix the C implementation of 'warnings' to infer the filename of the module that | Brett Cannon | 2008-05-03 | 1 | -0/+13 | 
| | | | | | | | | raised an exception properly when __file__ is not set, __name__ == '__main__', and sys.argv[0] is a false value. Closes issue2743. | ||||
| * | Fix some indentation errors. | Brett Cannon | 2008-05-03 | 1 | -9/+10 | 
| | | |||||
| * | Fix a backwards-compatibility mistake where a new optional argument for | Brett Cannon | 2008-05-02 | 1 | -3/+0 | 
| | | | | | | | | warnings.showwarning() was being used. This broke pre-existing replacements for the function since they didn't support the extra argument. Closes issue 2705. | ||||
| * | Added PyErr_WarnPy3k function. (issue 2671) I will be converting current ↵ | Benjamin Peterson | 2008-04-27 | 1 | -0/+9 | 
| | | | | | Py3k warnings to the use of this function soon. | ||||
| * | Correct a refleak found by "regrtest.py -R:: test_structmembers" | Amaury Forgeot d'Arc | 2008-04-14 | 1 | -5/+6 | 
| | | | | | | | Some other minor updates in _warnings.c: - make a function static - rename a shadowing local variable | ||||
| * | Use PyString_InternFromString instead of PyString_FromString for static vars | Christian Heimes | 2008-04-13 | 1 | -3/+3 | 
| | | |||||
| * | Re-implement the 'warnings' module in C. This allows for usage of the | Brett Cannon | 2008-04-12 | 1 | -0/+856 | 
| 'warnings' code in places where it was previously not possible (e.g., the parser). It could also potentially lead to a speed-up in interpreter start-up if the C version of the code (_warnings) is imported over the use of the Python version in key places. Closes issue #1631171. | |||||
