John T. Wodder II

Using a class as a `flag_value` causes the default to be instantiated in click 8.3.0

1

Consider the following code: ```python import click class Foo: pass class Bar: pass @click.command() @click.option("--foo", "ty", flag_value=Foo, type=click.UNPROCESSED, default=True) @click.option("--bar", "ty", flag_value=Bar, type=click.UNPROCESSED) def main(ty): click.echo(repr(ty)) if __name__ == "__main__":...

`ERR_INVALIDCAPCMD` not listed

2

[The Capability Negotiation specification](https://ircv3.net/specs/extensions/capability-negotiation.html) states in part: > If a client sends a subcommand which is not in the list above or otherwise issues an invalid command, then numeric 410...

ANSI colors for first 16 IRC colors?

3

[The "Colors" section of the "IRC Formatting" page](https://modern.ircdocs.horse/formatting#colors) lists recommended ANSI color codes for IRC colors 16 through 98 but not for colors 0 through 15, and I'm not 100%...

Is the `` parameter of [`RPL_UMODEIS`](https://modern.ircdocs.horse/#rplumodeis-221) guaranteed to be a valid [mode string production](https://modern.ircdocs.horse/#mode-message) — i.e., is it guaranteed to start with a `+` or `-`? I've observed that libera.chat...

Is the set of channel status symbols listed for [`RPL_NAMREPLY`](https://modern.ircdocs.horse/#rplnamreply-353) open or closed? That is, if I'm writing a client, should I only expect the symbols listed, or should any(?)...

Wildcard grammar does not allow masks like "`*ar`"

1

The ABNF for [wildcard expressions](https://modern.ircdocs.horse/#wildcard-expressions) currently requires that all occurrences of `*` or `?` be preceded by a non-backslash character; as a result, the grammar disallows masks that begin with...

[The documentation on numeric replies](https://modern.ircdocs.horse/#numerics) states: > Clients MUST NOT fail because the number of parameters on a given incoming numeric is larger than the number of parameters we list...

[The main-page documentation for the `CAP` command](https://modern.ircdocs.horse/#cap-message) currently lists its parameters as ` [:]`. However, according to the linked [Capability Negotiation specification](https://ircv3.net/specs/extensions/capability-negotiation.html), this format is only used for `CAP` messages...

Target of `NOTICE` can be `*`

2

[The documentation for the `NOTICE` message](https://modern.ircdocs.horse/#notice-message) currently states that its "`` is interpreted the same way as it is for the [`PRIVMSG`](https://modern.ircdocs.horse/#privmsg-message) command," and the documentation for `PRIVMSG` states that...

Syntax for server parameters to client messages?

1

Various client messages take one or more parameters that refer to servers (e.g., `CONNECT`, `SQUIT`, and `TIME`), but the documentation doesn't seem to describe the actual format of these parameters,...