Enhancement: properly parse return annotations with dangling comma, e.g. -> tuple[int,]
Is your feature request related to a problem? Please describe.
Functions with a return annotation including a dangling comma to represent an indeterminate number of elements are not properly documented. For example, def thing() -> tuple[int,] is documented as thing() -> tuple[int], misrepresenting the function as returning only a single value.
Describe the solution you'd like
It should be possible to detect this in the return annotation and document it properly.
Additional context
Happens for both Python 3.10 and 3.11rc1.
k98kurz / autodox
Tool for generating documentation automatically from code annotations, types, and docstrings.
2
Contributors get 50% of received funds after fees
How does funding with Polar work?
1
Pay now to fund the work behind this issue.
2
Get updates on progress being made.
3
Maintainer is rewarded once the issue is completed.
FAQ
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too