Weird unicode symbols on Windows

[cacharle]

This is what I get when I run this package:

$ pipx run bump-my-version -h

 Usage: bump-my-version [OPTIONS] COMMAND [ARGS]...

 Version bump your Python project.

Γò¡ΓöÇ Options ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓò«

I checked on different shells and terminals, the behavior is consistent.

I get this unicode gibberish for every command line output

[coordt]

The expected output is:

bump-my-version -h

 Usage: bump-my-version [OPTIONS] COMMAND [ARGS]...

 Version bump your Python project.

╭─ Options ──────────────────────────────────────────────────────────────────╮
│ --version        Show the version and exit.                                │
│ --help     -h    Show this message and exit.                               │
╰────────────────────────────────────────────────────────────────────────────╯
╭─ Commands ─────────────────────────────────────────────────────────────────╮
│ bump           Change the version.                                         │
│ replace        Replace the version in files.                               │
│ sample-config  Print a sample configuration file.                          │
│ show           Show current configuration information.                     │
│ show-bump      Show the possible versions resulting from the bump          │
│                subcommand.                                                 │
╰────────────────────────────────────────────────────────────────────────────╯

This looks like an issue with how your terminal displays Unicode.

I'm not sure how to help since I don't know how your terminal is configured.

[cacharle]

I tried on my machine: Wezterm/Powershell
and my colleague's machine: Default windows cmd

We both got the same result, I don't think this is a configuration thing since my colleague didn't modify his shell/terminal whatsoever

[cacharle]

Seems like rich-click has some issues on Windows: ewels/rich-click#300 and ewels/rich-click#165