[ 
https://issues.apache.org/jira/browse/SPARK-36845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17422371#comment-17422371
 ] 

Maciej Szymkiewicz edited comment on SPARK-36845 at 9/29/21, 8:13 PM:
----------------------------------------------------------------------

I'd recommend adding SPARK-36145 as blocker for this, so we can proceed cleanly 
with

{code:python}

from __future__ import annotations

{code}

and avoid all the quoting in in-lined annotations.




was (Author: zero323):
I'd recommend adding SPARK-36145 as blocker for this, so we can proceed cleanly 
with {{from __future__ import annotations}} and avoid all the quoting in 
inlined annotations.



> Inline type hint files
> ----------------------
>
>                 Key: SPARK-36845
>                 URL: https://issues.apache.org/jira/browse/SPARK-36845
>             Project: Spark
>          Issue Type: Umbrella
>          Components: PySpark, SQL
>    Affects Versions: 3.3.0
>            Reporter: Takuya Ueshin
>            Priority: Major
>
> Currently there are type hint stub files ({{*.pyi}}) to show the expected 
> types for functions, but we can also take advantage of static type checking 
> within the functions by inlining the type hints.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Reply via email to