Claudiu Popa

Thanks @ramkumarhn We should add a rule for this as well.

Hey @sushobhit27 I'm not sure who opted to work on this issue, but feel free to take it! The rough idea of this change would be: - first add mypy...

Sounds like a good plan to me, @AWhetter !

#2338 was merged but I'm not sure if we should close this issue now or after we have annotations for all the pylint code. Probably the latter as it's easier...

@AWhetter Definitely. Since that is not measurable enough, I'd say we can close this once we have annotations where it matters. It's important that we now have the setup for...

Sounds like a good improvement @nickdrozd This can be an optional check for now, in the form of an extension `pylint.checkers.extensions`, which needs to be explicitly enabled in the configuration...

@nickdrozd That approach sounds right to me. You should find some similar checks in `checkers.refactoring`, `consider-using-get` and `simplifiable-if-statement` come to mind.

This was just reported by another user at #767 I'll have a look. Hopefully we'll release a bug fix in the following day(s).

@bradmcl For the record, https://github.com/PyCQA/pylint/commit/a249d45bc55e18c893fc7a645ab60bb00417d5c1 should fix your problems.

Yup, added a milestone to the 2.0 release. Unfortunately, we don't know when that is going out, since the only people active are me and @ceridwen who is working more...