[ python-Bugs-1531415 ] parsetok.c emits warnings by writing to stderr

[SourceForge.net]

Bugs item #1531415, was opened at 2006-07-31 07:37
Message generated for change (Comment added) made by anthonybaxter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1531415&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Interpreter Core
Group: Python 2.5
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jp Calderone (kuran)
Assigned to: Nobody/Anonymous (nobody)
Summary: parsetok.c emits warnings by writing to stderr

Initial Comment:
Warnings should be emitted with the warning system, via
PyErr_Warn.


----------------------------------------------------------------------

>Comment By: Anthony Baxter (anthonybaxter)
Date: 2006-11-07 17:07

Message:
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.


----------------------------------------------------------------------

Comment By: Anthony Baxter (anthonybaxter)
Date: 2006-11-07 17:03

Message:
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.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1531415&group_id=5470