Given validator is a class, I'd expect to call a .validate method off it, rather than calling the class directly.

You can also call validate_password('hunter2', password_validators=[validator]), which whilst more verbose might be clearer.

Given validator is a class, I'd expect to call a .validate method off it, rather than calling the class directly.

I expect class-based validators (including password validators) to have the same logic because they do the exact same thing and follow the exact same naming "convention".
For example, Django default class RegexValidator implement .__call__() method for validating usage and don't even have .validate() method.

I think the overall goal of this PR makes sense, and I agree that it feels weird that auth's validators do not implement __call__ like core validators do.

@iamkorniichuk Since this is not a trivial PR, could you please create a ticket and follow the guidelines for contributing to Django? Specifically, besides the accepted ticket, this work would need tests and a small release note for 5.2.

Thank you both for your contributions! 🌟

@iamkorniichuk Since this is not a trivial PR, could you please create a ticket

I've done it.
Thanks for validating the idea. Hope it will be implemented!

@iamkorniichuk Since this is not a trivial PR, could you please create a ticket

I've done it. Thanks for validating the idea. Hope it will be implemented!

Thank you! Please note that this work needs tests and docs updates. Once those are completed, please remember to set the proper Trac flags in the ticket as described in the PR checklist when this is ready for re-review.