`too-few-public-methods` doesn't count dunder methods if inherited about pylint HOT 7 OPEN

Possibly related: #9420

from pylint.

ABC1 has an additional public method "getitem". Is that what you find unexpected that pylint counted?

from pylint.

class Test has two public methods: __getitem__ and method1 (no warning, as expected)
class MyABC1 has two public methods: getitem and method1 (no warning, as expected)
class MyABC2 has two public methods: __getitem__ and method1 (no warning, as expected)
class Concrete1 implements the abstract method method1 of MyABC1 (no warning, as expected)
class Concrete2 implements the abstract method method1 of MyABC2 (warning, unexpected)

from pylint.

Ah, if the difference is just that too-few-public-methods thinks anything that starts with _ is private even if it's a dunder, then that's just #9420.

from pylint.

According to this logic ("too-few-public-methods thinks anything that starts with _ is private"), then there should be a warning for class Test - but there is not. (same for class MyABC2)

from pylint.

Apologies, I took #9420 at face value, but I cannot reproduce the behavior described there. Dunders besides __init__() are counted as public methods, so that explains why Test doesn't raise a warning.

from pylint.

Apparently, inherited dunders are not counted. If that's the part you'd like us to reconsider, I'm happy to reopen the issue for additional discussion.

from pylint.