print statement is highlighted by pylint

[noonedeadpunk]

Environment data

VS Code version: 1.19.3
Python Extension version: 2018.1
Python Version: 2.7, 3.5
OS and version: OS independent

Actual behavior

pylint marks print statement and print() function are marked as error on both python 2.7 and python 3.5. This behavior appeared just after module upgrade to 2018.1

Expected behavior

pylint shouldn't mark error if using print() function on any python version and print statement on python 2.7

Steps to reproduce:

• create new .py file
• enter print("Hello, world!")
• save file
  

Logs

Output from Python output panel

[pylint]E1601:print statement used (1, 1)

Output from Console window (Help->Developer Tools menu)

console.ts:123 [Extension Host] Python Extension: Failed to get conda info from conda null
t.log @ console.ts:123
console.ts:123 [Extension Host] (node:16735) DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.

[MikhailArkhipov]

This is PyLint message. Extension simply outputs what PyLint produces. In 2.7 the message should appear according to PyLint docs:
https://pylint.readthedocs.io/en/latest/technical_reference/features.html

print-statement (E1601):
  print statement used (print is a function in Python 3)

However, it should not appear in 3+ then. You can suppress the message in pylintrc file.

[noonedeadpunk]

But it seems, that according to pylint, this message should be printed only if print is used as the statement, while it marks as an error while using print as a function.

Moreover, I couldn't reproduce this with system pylint (which is installed on the same machine, as the affected VS Code):

dimar@SVTech-Workstation:~/Documents/Python$ /usr/bin/pylint --version
No config file found, using default configuration
pylint 1.5.2, 
astroid 1.4.4
Python 2.7.12 (default, Dec  4 2017, 14:50:18) 
[GCC 5.4.0 20160609]
dimar@SVTech-Workstation:~/Documents/Python$ /usr/bin/pylint test.py
No config file found, using default configuration
************* Module test
C:  1, 0: Unnecessary parens after 'print' keyword (superfluous-parens)
C:  1, 0: Missing module docstring (missing-docstring)


Report
======
1 statements analysed.

Statistics by type
------------------

+---------+-------+-----------+-----------+------------+---------+
|type     |number |old number |difference |%documented |%badname |
+=========+=======+===========+===========+============+=========+
|module   |1      |1          |=          |0.00        |0.00     |
+---------+-------+-----------+-----------+------------+---------+
|class    |0      |0          |=          |0           |0        |
+---------+-------+-----------+-----------+------------+---------+
|method   |0      |0          |=          |0           |0        |
+---------+-------+-----------+-----------+------------+---------+
|function |0      |0          |=          |0           |0        |
+---------+-------+-----------+-----------+------------+---------+



Raw metrics
-----------

+----------+-------+------+---------+-----------+
|type      |number |%     |previous |difference |
+==========+=======+======+=========+===========+
|code      |1      |50.00 |NC       |NC         |
+----------+-------+------+---------+-----------+
|docstring |0      |0.00  |NC       |NC         |
+----------+-------+------+---------+-----------+
|comment   |0      |0.00  |NC       |NC         |
+----------+-------+------+---------+-----------+
|empty     |1      |50.00 |NC       |NC         |
+----------+-------+------+---------+-----------+



Duplication
-----------

+-------------------------+------+---------+-----------+
|                         |now   |previous |difference |
+=========================+======+=========+===========+
|nb duplicated lines      |0     |NC       |NC         |
+-------------------------+------+---------+-----------+
|percent duplicated lines |0.000 |NC       |NC         |
+-------------------------+------+---------+-----------+



Messages by category
--------------------

+-----------+-------+---------+-----------+
|type       |number |previous |difference |
+===========+=======+=========+===========+
|convention |2      |0        |+2.00      |
+-----------+-------+---------+-----------+
|refactor   |0      |0        |=          |
+-----------+-------+---------+-----------+
|warning    |0      |0        |=          |
+-----------+-------+---------+-----------+
|error      |0      |1        |-1.00      |
+-----------+-------+---------+-----------+



Messages
--------

+-------------------+------------+
|message id         |occurrences |
+===================+============+
|superfluous-parens |1           |
+-------------------+------------+
|missing-docstring  |1           |
+-------------------+------------+



Global evaluation
-----------------
Your code has been rated at -10.00/10

dimar@SVTech-Workstation:~/Documents/Python$

And if I replace print() with a statement, only "Missing module docstring (missing-docstring)" notification will stay. So this is possible only if the module uses it's own pylint, which is different version from the system one.

It seems, that it's my fault about reporting problem for python3 - pylint just hadn't re-read the file after changing Python version. So this problem is referenced only to python2.

[zerkms]

@noonedeadpunk run pylint with these arguments

--disable=all --enable=F,E,unreachable,duplicate-key,unnecessary-semicolon,global-variable-not-assigned,unused-variable,unused-wildcard-import,binary-op-exception,bad-format-string,anomalous-backslash-in-string,bad-open-mode --reports=n --output-format=text --msg-template='{line},{column},{category},{msg_id}:{msg}'

[noonedeadpunk]

@zerkms Yep, you're right, enabling "E" raises "print statement used". Most likely, that vscode-python used other list of enabled modules before update, as this problem appeared only after module update.

And it's pretty irritating, as all of projects are highlighted due to "print statement used". But it seems, that the problem should be addressed to the pylint.

[zerkms]

@noonedeadpunk if you report it to the pylink could you please post a link here

[noonedeadpunk]

@zerkms it seems, that this actual problem with pylint started some time ago, but only now it started to annoy in vscode. Probably you know if --enable=E (or probably some other option) was added by default with the module update?

So, from __future__ import print_function resolves problem, but it looks more like workaround, than the real solution.

[zerkms]

I personally use logger instead of print ;-)

[noonedeadpunk]

Actually, something is really became wrong with pylint after module upgrade. I suppose, that the point is in the default flags for pylint.

So, when I enabled all flags locally for file, which were kindly provided by @zerkms I recieved the following result (which is absolutely correct, except print statement error, which is seemed to be really pylint problem, when -E(--error-mode) flag is used):

But if I will remove this pylint options string, all other notifications will be suppressed. If I will remove print() statement, pylint won't display suppressed problems at all.
And I am 100% sure, that these notifications were shown before the module update