A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2016-February/143188.html below:

[Python-Dev] Issue #26204: compiler now emits a SyntaxWarning on constant statement

[Python-Dev] Issue #26204: compiler now emits a SyntaxWarning on constant statementJohn Mark Vandenberg jayvdb at gmail.com
Mon Feb 8 16:37:01 EST 2016
On Tue, Feb 9, 2016 at 8:20 AM, Victor Stinner <victor.stinner at gmail.com> wrote:
> Le 8 févr. 2016 9:34 PM, "Guido van Rossum" <guido at python.org> a écrit :
>> If you want to do linter integration that should probably be
>> integrated with the user's editor, like it is in PyCharm, and IIUC
>> people can do this in e.g. Emacs, Sublime or Vim as well. Leave the
>> interpreter alone.
>
> In GCC, warnings are welcome because it does one thing: compile code. GCC is
> used by developers. Users use the produced binary.
>
> In Python, it's different because it executes code and runs code. It's used
> by developers and users.
>
> It's more tricky to make choices like showing or not deprecation warnings.
>
> It looks like most Python developers prefer to use an external linter.

fwiw, pyflakes doesnt detect this.  I've created a bug for that

https://bugs.launchpad.net/pyflakes/+bug/1543246

-- 
John Vandenberg
More information about the Python-Dev mailing list

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