You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@beam.apache.org by GitBox <gi...@apache.org> on 2022/11/02 19:47:57 UTC

[GitHub] [beam] TheNeuralBit opened a new issue, #23950: [Task]: Normalize `typehint` vs. `type-hint` vs. `type hint` in Python documentation and docstrings

TheNeuralBit opened a new issue, #23950:
URL: https://github.com/apache/beam/issues/23950

   ### What needs to happen?
   
   See https://github.com/apache/beam/pull/23909#discussion_r1011974873
   
   We use three different formats to represent "type hint" in Python documentation and docstrings. We should pick one and standardize on it across all documentation on the Beam website and in docstrings.
   
   ### Issue Priority
   
   Priority: 3
   
   ### Issue Component
   
   Component: website


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [beam] ayushthe1 commented on issue #23950: [Task]: Normalize `typehint` vs. `type-hint` vs. `type hint` in Python documentation and docstrings

Posted by GitBox <gi...@apache.org>.
ayushthe1 commented on issue #23950:
URL: https://github.com/apache/beam/issues/23950#issuecomment-1303108748

   .take-issue


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [beam] TheNeuralBit commented on issue #23950: [Task]: Normalize `typehint` vs. `type-hint` vs. `type hint` in Python documentation and docstrings

Posted by GitBox <gi...@apache.org>.
TheNeuralBit commented on issue #23950:
URL: https://github.com/apache/beam/issues/23950#issuecomment-1305656239

   I think we may want to standardize on "type hint" in documentation and "typehint" for code. For reference: [PEP 484](https://peps.python.org/pep-0484/) uses "type hint".


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [beam] ayushthe1 commented on issue #23950: [Task]: Normalize `typehint` vs. `type-hint` vs. `type hint` in Python documentation and docstrings

Posted by GitBox <gi...@apache.org>.
ayushthe1 commented on issue #23950:
URL: https://github.com/apache/beam/issues/23950#issuecomment-1304545227

   hey @TheNeuralBit , i made a pr for this issue. Could you please review it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org