[easy] New rules for assignment to __bases__

[pylint-bot]

Originally reported by: Claudiu Popa (BitBucket: PCManticore, GitHub: @PCManticore)

---

• can assign only tuples to __bases__

#!python

class A: pass
A.__bases__ = "lala"

• can assign only non empty tuples to __bases__

#!python

class A: pass
A.__bases__ = ()

• __bases__ must be tuple of classes

#!python

class A: pass
A.__bases__ = (1, )

---

• Bitbucket: https://bitbucket.org/logilab/pylint/issue/584

[clavedeluna]

I'll work on this issue.

[clavedeluna]

I've closed the related PR. Agreement on that PR is that it isn't worth adding this check since mypy is doing the same thing. Discussion between naive v. non-naive approach in PR.

I think it would be fine to close this issue or at the very least update the labels (not a good first issue).

[clavedeluna]

Given I worked on this last, I'm going to close this issue. We discussed that it's not worth doing the naive approach since that's what mypy does, and doing the "hard" approach is pretty hard. I also hope this is a pretty rare pattern.

If anyone disagrees feel free to re-open.

[clavedeluna]

Guess I never did close this....