Incorrect 'unsubscriptable-object' reported

[qsmy41]

Steps to reproduce

Running Pylint on the following code will produce the error on the last line.

import statsmodels.api as sm

data = sm.datasets.longley.load_pandas().data

properties = ['GNP', 'POP']
specificData = data[properties]

Current behavior

Running Pylint gives

example.py|6 col 16 error| E1136: Value 'data' is unsubscriptable (unsubscriptable-object)
example.py|6 col 16 error| unsubscriptable-object: Value 'data' is unsubscriptable

Expected behavior

No errors/warnings should be produced.

pylint --version output

pylint 2.5.2
astroid 2.4.1
Python 3.7.7 (default, Apr 14 2020, 11:51:19)
[Clang 11.0.0 (clang-1100.0.33.12)]

[beauxq]

Same problem with this:

import numpy as np

ARRAY = np.array([[1, 2, 3]]).T

print(ARRAY[0])

Value 'ARRAY' is unsubscriptable (unsubscriptable-object)
There should be no error.

[Cielquan]

Have a similar problem with type hints.

This LoC

EnvVarTypes = Union[str, int, float, bool, None]

gives E1136: Value 'Union' is unsubscriptable (unsubscriptable-object).

This LoC

def validate(self, line: str, _: GitCommit) -> List[Optional[RuleViolation]]:

gives E1136: Value 'Optional' is unsubscriptable (unsubscriptable-object).

BUT those errors only occur in with

$ pylint --version
pylint 2.6.0
astroid 2.4.2
Python 3.9.0 (default, Oct  6 2020, 02:47:17) 
[GCC 7.5.0]

and not with

$ pylint --version
pylint 2.6.0
astroid 2.4.2
Python 3.8.6 (default, Oct  6 2020, 03:22:36) 
[GCC 7.5.0]

[leycec]

This also breaks PEP 560 and PEP 585. See this comment at the related issue #3882.

[hippo91]

@beauxq thanks for your comment. It seems your issue is not linked to the original one. Morevoer it should have been fixed through pylint-dev/astroid#831.

[hippo91]

@Cielquan thanks for your report. However your issue is not linked to the original one but it is due to the fact pylint is not yet supporting python3.9. We are working on it.

[hippo91]

To any people thinking adding a comment here, please do only if your problem seems to be linked to panda's support in pylint. Otherwise please open another issue. Thanks.

[MiltiadisKoutsokeras]

Another case that breaks our code checking CI/CD:

"""Pylint unsubscriptable-object example"""
import pandas as pd

result = pd.DataFrame()
cols = ['a', 'b', 'c', 'd']
CSVDATA = 'data.csv'
df = pd.read_csv(CSVDATA)
df['d'] = [CSVDATA.split('.', maxsplit=1)[0]] * df.shape[0]
result = pd.concat([result, df[cols]], axis=0)
print(result)

Pylint reports:

************* Module pylint_wrong
pylint_wrong.py:9:28: E1136: Value 'df' is unsubscriptable (unsubscriptable-object)

------------------------------------------------------------------
Your code has been rated at 3.75/10 (previous run: 3.75/10, +0.00)

[bhargavgohil25]

@MiltiadisKoutsokeras got any solution to remove this error ? I am facing the same but on initializing i.e on pd.DataFrame()

[juliangilbey]

For those trying to fix this issue, the case I reported in #6942 may be useful:

import pandas as pd  # type: ignore

df = pd.read_csv("data.csv")

df_a = df.drop(columns=["a"])
df_b = df["b"]

gives an unsubscriptable-object error message, but swapping the lines doesn't:

import pandas as pd  # type: ignore

df = pd.read_csv("data.csv")

df_b = df["b"]
df_a = df.drop(columns=["a"])

Hope this helps!

[wclark]

I ran into this issue myself, and after looking over some examples here and in related/duplicated tickets, I have a hunch that the cause is that methods like drop (or in my case, set_index) don't always return a DataFrame -- sometimes they return None, per the Pandas API. If you force the methods to return None (by passing an inplace=True parameter) and restructure your code accordingly, this error seems to go away.

I'd argue this is still something to fix in Pylint, because these Pandas methods ONLY seem to return None when inplace=True is passed -- which Pylint could (and arguably should) easily check.