Bug: NoSuchOption.format_message() returns tuple repr instead of plain string

[foomunleong]

First Check

• I added a very descriptive title here.
• I used the GitHub search to find a similar question and didn't find it.
• I searched the documentation, with the integrated search.
• I already searched in Google "How to X" and didn't find any information.
• I already read and followed all the tutorials in the docs and didn't find an answer.

Example Code

from typer._click.exceptions import NoSuchOption

exc = NoSuchOption("--fooo", possibilities=["--foo"])
print(exc.format_message())
# Current:  No such option: --fooo ('(Possible options: --foo)',)
# Expected: No such option: --fooo (Possible options: --foo)

Description

Bug

NoSuchOption.format_message() in typer/_click/exceptions.py produces a tuple
repr in its output instead of a plain string when possibilities is non-empty.

Current output:
Error: No such option: --fooo ('(Possible options: --foo)',)

Expected output:
Error: No such option: --fooo (Possible options: --foo)

Root cause

In typer/_click/exceptions.py, the suggest variable is assigned a 1-element
tuple due to a trailing comma:

# Current (buggy)
suggest = (f"(Possible options: {possibility_str})",)  # trailing comma → tuple
return f"{self.message} {suggest}"

When suggest (a tuple) is interpolated into the f-string, Python renders it as
('(Possible options: ...)',) rather than (Possible options: ...).

Proposed fix

Remove the trailing comma so suggest is a plain string:

# Fixed
suggest = f"(Possible options: {possibility_str})"
return f"{self.message} {suggest}"

This matches the behaviour of the upstream Click library's own NoSuchOption.

Operating System

macOS

Operating System Details

No response

Project Version

master

Python Version

No response

Additional Context

No response

[svlandeg]

Thanks for the report! While we continue refactoring on top of the vendored Click, things might still change a bit, especially these error messages. They might not stay exactly the same.

That said, it does look like this particular comma is a bug and can be removed. Feel free to PR this!

[foomunleong]

Thanks, PR created: #1843