Ethan Furman ethan at stoneleaf.us
Tue Aug 16 13:43:12 EDT 2011

• Previous message (by thread): Why no warnings when re-assigning builtin names?
• Next message (by thread): Why no warnings when re-assigning builtin names?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

Seebs wrote:
> 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.

With gcc you pay the cost once, with Python you would pay it with every 
run.  A linter would be more along the lines of 'pay it once'.

~Ethan~

---

• Previous message (by thread): Why no warnings when re-assigning builtin names?
• Next message (by thread): Why no warnings when re-assigning builtin names?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-list mailing list