You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Windows with the default legacy console encoding (cp1252), any command whose help text contains non-ASCII characters (e.g. → in the search --help text) crashes with UnicodeEncodeError instead of printing help.
File "click\utils.py", line 539, in echo
UnicodeEncodeError: 'charmap' codec can't encode character '\u2192' in position 694
[PYI-10896:ERROR] Failed to execute script 'commands'
Expected result
Help text prints without crashing (arrow rendered or gracefully replaced).
Notes
Actual commands (search, extract, ...) work fine; only output containing non-ASCII characters is affected.
A likely fix is configuring stdout/stderr with errors="backslashreplace" at CLI startup so unencodable characters degrade gracefully on legacy code pages. Happy to open a PR if you're open to it!
Summary
On Windows with the default legacy console encoding (cp1252), any command whose help text contains non-ASCII characters (e.g.
→in thesearch --helptext) crashes withUnicodeEncodeErrorinstead of printing help.Environment
npm install -g parallel-web-cliSteps to reproduce
Actual result
Expected result
Help text prints without crashing (arrow rendered or gracefully replaced).
Notes
search,extract, ...) work fine; only output containing non-ASCII characters is affected.errors="backslashreplace"at CLI startup so unencodable characters degrade gracefully on legacy code pages. Happy to open a PR if you're open to it!