not-callable: false positive due to conflit between "next" user-function and "collections.abc"

[bansan85]

Steps to reproduce

from collections.abc import Callable


class Class:
    def next(self):
        pass

    def __init__(self):
        self.next()

Current behavior

self.next is not callable

These is no warning if I remove the line from collections.abc import Callable

Expected behavior

No warning message.

pylint --version output

pylint 2.6.0
astroid 2.4.2
Python 3.9.0 (tags/v3.9.0:9cf6752, Oct  5 2020, 15:34:40) [MSC v.1927 64 bit (AMD64)]

[hippo91]

@bansan85 thanks for your report. I can reproduce it with the following snippet:

#pylint: disable=missing-module-docstring, missing-function-docstring
#pylint: disable=missing-class-docstring, too-few-public-methods
from collections.abc import Callable


class Class(Callable):
    def __call__(self, *args, **kwargs):
        pass

    def next(self):
        pass

    def __init__(self):
        self.next()

[exquo]

Looks like this affects the whole collections package, rather than just the Callable class or the collections.abc module.
Replacing import line with

import collections

reports the same pylint error.

I believe this is a manifestation of #4221 caused by these lines in __init__.py: (1), (2).

The current issue is probably the cause of #3595 and various comments in it. All it takes to get the error is import collections (or import something that in turn imports collections), and call <anything>.next() or <anything>.prev().