This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author methane
Recipients JelleZijlstra, barry, eric.smith, gvanrossum, kj, larry, lukasz.langa, methane, xtreak
Date 2021-04-24.07:56:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
> The difference between eval_str=True and eval_str=ONLY_IF_STRINGIZED:
> def foo(a:int, b:"howdy howdy"): ...
> inspect.get_annotations(foo, eval_str=True) throws an exception.
> inspect.get_annotations(foo, eval_str=ONLY_IF_STRINGIZED) returns {'a': int, b: 'howdy howdy'}
> Type hints have a convention that string annotations are a "forward declaration" and should be eval()uated.  Annotations don't have such a convention--a string is a legal annotation, and is not required to be valid Python.

For such use case, ONLY_IF_STRINGIZED thorows an exception for `def
foo(a: "howdy howdy")` anyway.
In such cases, they should use `eval_str=False`, or `eval_str=True`
*and* `return_str_when_eval_failed=True` option.
Date User Action Args
2021-04-24 07:56:55methanesetrecipients: + methane, gvanrossum, barry, larry, eric.smith, lukasz.langa, JelleZijlstra, xtreak, kj
2021-04-24 07:56:55methanelinkissue43817 messages
2021-04-24 07:56:55methanecreate