Closed lucasiscovici2 closed 2 years ago
Could you explain what problem this PR is solving? How is doing analysis on the function's type signature helpful? Ideally, an explanation for why this is useful would include examples, a brief cost-benefit analysis (e.g. how difficult would this change be to maintain), and an explanation of alternative solutions.
Could you explain what problem this PR is solving? How is doing analysis on the function's type signature helpful? Ideally, an explanation for why this is useful would include examples, a brief cost-benefit analysis (e.g. how difficult would this change be to maintain), and an explanation of alternative solutions.
@terrencepreilly https://github.com/terrencepreilly/darglint/pull/194#issue-1106148726
@terrencepreilly maybe the best is to use astunparse (Until python 3.8) and ast.unparse (From python 3.9) ?
@terrencepreilly maybe the best is to use astunparse (Until python 3.8) and ast.unparse (From python 3.9) ?
@terrencepreilly i create the pr #195 for this solution 🙂
Hello, and thank you for dev Darglint 🙂 This Pr is intended to allow more complicated types hints to be detected for parameters and return. (With "[") Ex: List[int], Union[int, str], ....
TODO :
Explanation :
Why ast.parse/ast.dump ?
Pb ?
Alternatives :
Even if it's a draft, I would like your corrections/comments ✍🏻 🙂
Ex: test.py