Batuhan Taskaya <isidenti...@gmail.com> added the comment:
> So I don't feel as strongly about that.
Just to note, since I believe the solution for all this might be the same (not
processing annotations at all, since they will be compiled to strings in the
later stage). If we go down on that route, it will be simpler but we won't be
able to raise SyntaxError's for "a: (yield)" / "b: (await/yield from x)".
By the way, this is what happens if you try to use get_type_hints on a function
where an argument is (yield):
>>> typing.get_type_hints(a)
Traceback (most recent call last):
File "/usr/local/lib/python3.10/typing.py", line 537, in __init__
code = compile(arg, '<string>', 'eval')
File "<string>", line 1
SyntaxError: 'yield' outside function
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/local/lib/python3.10/typing.py", line 1490, in get_type_hints
value = ForwardRef(value)
File "/usr/local/lib/python3.10/typing.py", line 539, in __init__
raise SyntaxError(f"Forward reference must be an expression -- got {arg!r}")
SyntaxError: Forward reference must be an expression -- got '(yield)'
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue42725>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
