Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

1-element tuple rendered incorrectly #9364

Closed
timhoffm opened this issue Jun 19, 2021 · 0 comments
Closed

1-element tuple rendered incorrectly #9364

timhoffm opened this issue Jun 19, 2021 · 0 comments

Comments

@timhoffm
Copy link
Contributor

Describe the bug
This is a followup to #7964 which has been addressed in #8265.

However the special case of a 1-element tuple is still not handled correctly.

(1,) is rendered as (1), but should keep the trailing comma.

To Reproduce
Add a testcase

    ("(1,)", "(1,)"),                           # Tuple (single element)

at

("()", "()"), # Tuple (empty)

@tk0miya tk0miya added this to the 4.1.0 milestone Jun 20, 2021
tk0miya added a commit that referenced this issue Jun 30, 2021
Fix #9364: autodoc: 1-element tuple on the defarg is wrongly rendered
hkuno pushed a commit to hkuno/sphinx that referenced this issue Jul 11, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 31, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants