Ramon Saraiva

@aniav are you working (or still going to work) on this?

Should we take the opportunity to just upgrade Python to 3.9.x?

Hey @jacobtylerwalls - landing here from the `hacktoberfest` label and not familiar with pylint's codebase. Is this a similar implementation as `_check_lru_cache_decorators` in `StdlibChecker`?

Awesome, I'll be reading more about how everything works and attempt to come up with a draft patch for this. A few review interactions will most likely be needed. Thanks!

Created that draft PR and added in its description a bit of my thought process and things that I believe can be improved and simplified. I just want to have...

I think https://github.com/PyCQA/pylint/commit/4d95d21ad41e1a219cc5917181b102e5de5832bd and https://github.com/PyCQA/pylint/commit/cc64ded7c6c5e5fd053e5a58fbbeebce0cff93c8 bring a much cleaner version that https://github.com/PyCQA/pylint/commit/3dc361624cd805e32972372257e3ee48ef1ac84a had - still open to suggestions. I added a new util function for `singledispatchmethod` (similar to the `singledispatch`...

hey @jenkoian - is the image supposed to be a screenshot or something similar of the logo from this https://github.com/jenkoian/hacktoberfest-checker/blob/master/hacktoberfest-checker-2022.png?

@marksweb @marksweb thoughts?

I can agree with that too, we can also make the unique constraint only apply when e-mail is not null. Something similar to: ```python models.UniqueConstraint( fields=["form", "email"], condition=models.Q(email__isnull=False), ... )...

@marksweb I think that `UniqueConstraint` fields and conditions are available for a long time.. At least 2.2