Fix too-many-ancestors

[cdce8p]

Steps

• Add yourself to CONTRIBUTORS if you are a new contributor.
• Add a ChangeLog entry describing what your PR does.
• If it's a new feature or an important bug fix, add a What's New entry in
  doc/whatsnew/<current release.rst>.
• Write a good description on what the PR does.

Description

Fix false-positive too-many-ancestors by ignoring pre-defined builtin classes when calculating the number of ancestors. The list isn't complete but should cover most cases.

Type of Changes

	Type
✓	🐛 Bug fix

Related Issue

Closes #4166
Closes #4415

[coveralls]

Coverage increased (+0.001%) to 91.642% when pulling 3bbbaa1 on cdce8p:fix-too-many-ancestors into 28c093c on PyCQA:master.

[Pierre-Sassoulas]

Good job !

[Pierre-Sassoulas]

This actually fixed that test case too, the correct number IS 8 !

[cdce8p]

Depends if you con't object, but it's certainly not false.

[SagaraBattousai]

I also get this error when inheriting from any normal class (which doesn't cause this error) and a Protocol (which while not necessary is nice to ensure we override the required functions). Whilst we only inherit directly from two classes we get too-many-ancestors 8/7.

This error can be reproduced by:
from setuptools.command.build import SubCommand
from setuptools.command.build_ext import build_ext

# Sub Command is a Protocol but we want to explicitly inherit
class Foo(build_ext, SubCommand):
.....

[Pierre-Sassoulas]

@SagaraBattousai please open a new issue your comment on a closed issue is going to get lost.