Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/1999-September/000810.html below:

[Python-Dev] Catching "return" and "return expr" at compile time

• Previous message: [Python-Dev] Catching "return" and "return expr" at compile time
• Next message: [Python-Dev] Catching "return" and "return expr" at compile time
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This is a valuable service!  Even though I'm sure that it will cause
some pain for people who were used to this programming style...

I'm not sure I like the fact that you can't turn it off --
traditionally, Python has had a "no warnings" policy.  That has been
diluted a bit (python -t prints warnings) but so far it has been the
default.

I'm wondering if we should introduce a general '-w' flag to turn on
warnings like this (which would subsume -t)?  Or perhaps there should
be a -W flag ("no warnings") and warnings should be the default?

There are also platform problems, e.g. on the Mac, stderr doesn't
always exist, and on Windows, it doesn't exist if pythonw.exe is
used...

--Guido van Rossum (home page: http://www.python.org/~guido/)

• Previous message: [Python-Dev] Catching "return" and "return expr" at compile time
• Next message: [Python-Dev] Catching "return" and "return expr" at compile time
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4