Created on 2006-07-30 21:37 by kuran, last changed 2010-08-09 03:34 by terry.reedy.
| Messages (4) | |||
|---|---|---|---|
| msg60952 - (view) | Author: Jp Calderone (kuran) | Date: 2006-07-30 21:37 | |
Warnings should be emitted with the warning system, via PyErr_Warn. |
|||
| msg60953 - (view) | Author: Anthony Baxter (anthonybaxter) | Date: 2006-11-07 06:03 | |
Logged In: YES user_id=29957 Should we change these to all just default to a SyntaxWarning? I agree that just spitting out warnings to stderr is extremely suboptimal. |
|||
| msg60954 - (view) | Author: Anthony Baxter (anthonybaxter) | Date: 2006-11-07 06:07 | |
Logged In: YES user_id=29957 Neal points out there could be a bootstrapping problem if warnings.py needs to be imported. We could do something like check for 'warnings' in sys.modules, and still default to stderr if it's not been imported. A more thorough fix is to get warnings.py converted to C code, but that's going to be a 2.6 thing, not a 2.5.1 thing. |
|||
| msg113367 - (view) | Author: Terry J. Reedy (terry.reedy) *  |
Date: 2010-08-09 03:34 | |
warning.py it still is in 3.1 |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2010-08-09 03:34:27 | terry.reedy | set | nosy:
+ terry.reedy messages: + msg113367 versions: + Python 3.2, - Python 3.1, Python 2.7 |
| 2009-03-30 04:35:49 | ajaksu2 | set | nosy:
+ brett.cannon versions: + Python 3.1, Python 2.7, - Python 2.5 type: enhancement stage: test needed |
| 2006-07-30 21:37:34 | kuran | create | |