Re: [Python-Dev] Re: A warning switch?
What about adding a command-line switch for enabling warnings, as has been suggested long ago? The .append() change could then print a warning in 1.6alphas (and betas?), but still run, and be turned into an error later.
That's better. I propose that the warnings are normally on, and that there are flags to turn them off or thrn them into errors.
Can we then please have an interface to the "give warning" call (in stead of a simple fprintf)? On the mac (and possibly also in PythonWin) it's probably better to pop up a dialog (possibly with a "don't show again" button) than do a printf which may get lost. -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.oratrix.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm
Can we then please have an interface to the "give warning" call (in stead of a simple fprintf)? On the mac (and possibly also in PythonWin) it's probably better to pop up a dialog (possibly with a "don't show again" button) than do a printf which may get lost.
Sure. All you have to do is code it (or get someone else to code it). <0.9 wink> --Guido van Rossum (home page: http://www.python.org/~guido/)
Can we then please have an interface to the "give warning" call (in stead of a simple fprintf)? On the mac (and possibly also in PythonWin) it's probably better to pop up a dialog (possibly with a "don't show again" button) than do a printf which may get lost.
Sure. All you have to do is code it (or get someone else to code it).
How about just having either a "sys.warning" function, or maybe even a sys.stdwarn stream? Then a simple C API to call this, and we are done :-) sys.stdwarn sounds OK - it just defaults to sys.stdout, so the Mac and Pythonwin etc should "just work" by sending the output wherever sys.stdout goes today... Mark.
participants (3)
-
Guido van Rossum
-
Jack Jansen
-
Mark Hammond