I think the use case (for x.is_foo()) is rare. And instead of writing x.is_foo(x), if you make the guard a function you can write is_foo(x).
On Thu, Feb 11, 2021 at 6:51 PM Sebastian Kreft <[email protected]> wrote: > I still think that we should reconsider deferring what happens to class > and instance methods. > > The arguments given in https://www.python.org/dev/peps/pep-0647/#id13 > seem insufficient, specially considering than the workaround provided is > quite awkward. > > The author suggests to write def check(self, self2) -> Typeguard[T] and > call it as self.check(self). > _______________________________________________ > Python-Dev mailing list -- [email protected] > To unsubscribe send an email to [email protected] > https://mail.python.org/mailman3/lists/python-dev.python.org/ > Message archived at > https://mail.python.org/archives/list/[email protected]/message/CA2MFS4XXDPC6PDBW53BZWLWEMQOBBP6/ > Code of Conduct: http://python.org/psf/codeofconduct/ > -- --Guido van Rossum (python.org/~guido) *Pronouns: he/him **(why is my pronoun here?)* <http://feministing.com/2015/02/03/how-using-they-as-a-singular-pronoun-can-change-the-world/>
_______________________________________________ Python-Dev mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/MSGSGFJ6TBZMJBFZTQ5ORIAQH26TFZK3/ Code of Conduct: http://python.org/psf/codeofconduct/
