Why no warnings when re-assigning builtin names?

Seebs usenet-nospam at seebs.net
Tue Aug 16 19:11:38 CEST 2011

On 2011-08-16, Ethan Furman <ethan at stoneleaf.us> wrote:
> I think warnings should be reserved for language changes and such (like 
> DeprecationWarning, RuntimeWarning, and FutureWarning), not for possible 
> programmer mistakes.

I disagree, on the basis of the following:

The quality of C code I have to deal with has increased dramatically as
gcc's aggressive use of warnings has spread.

> Python can be improved -- I don't see 'hand-holding' as an improvement. 
>   IDEs and lints can do this.

-W ignore

Copyright 2011, all wrongs reversed.  Peter Seebach / usenet-nospam at seebs.net
http://www.seebs.net/log/ <-- lawsuits, religion, and funny pictures
http://en.wikipedia.org/wiki/Fair_Game_(Scientology) <-- get educated!
I am not speaking for my employer, although they do rent some of my opinions.

More information about the Python-list mailing list