On Mon, Apr 12, 2021 at 7:47 PM Paul Bryan <pbr...@anode.ca> wrote: > In 3.9 this cost is paid once when a type is defined. However, in 3.10, it > gets expensive, because when the string is evaluated by get_type_hints, its > result is not stored/cached anywhere (repeated calls to get_type_hints > results in repeated evaluation). As a workaround, I have code to "affix" > the evaluated expression in __annotations__ value. PEP 649 would resolve > this and eliminate the need for such a hack. >
Why not submit a PR that adds caching to get_type_hints(), rather than promote a paradigm shift? -- --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 -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/ZFZYGX6WHC5FYWGLNYVDFDS3MQ7BOQ4T/ Code of Conduct: http://python.org/psf/codeofconduct/
