[GH-ISSUE #97] QEMU exec commands parsed incorrectly on Windows #48

New issue

Closed

opened 2026-02-27 15:46:10 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 15:46:10 +03:00

Owner

Originally created by @r3d07 on GitHub (Apr 26, 2022).
Original GitHub issue: https://github.com/proxmoxer/proxmoxer/issues/97

#90 caused a regression when running Proxmoxer on Windows hosts. shlex is designed for *nix systems, not Windows. As a result, commands that previous worked on <1.3.0 now fail due to improper escaped characters.

The behavior described in this StackOverflow ticket describes the incorrect behavior:
https://stackoverflow.com/questions/19719971/why-do-i-need-4-backslashes-in-a-python-path

Before using shlex the OS should be checked to ensure that it is *nix and not Windows.

Originally created by @r3d07 on GitHub (Apr 26, 2022). Original GitHub issue: https://github.com/proxmoxer/proxmoxer/issues/97 #90 caused a regression when running Proxmoxer on Windows hosts. `shlex` is designed for *nix systems, not Windows. As a result, commands that previous worked on <1.3.0 now fail due to improper escaped characters. The behavior described in this StackOverflow ticket describes the incorrect behavior: https://stackoverflow.com/questions/19719971/why-do-i-need-4-backslashes-in-a-python-path Before using `shlex` the OS should be checked to ensure that it is *nix and not Windows.

kerem closed this issue

2026-02-27 15:46:10 +03:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/proxmoxer#48

No description provided.

Rows
Columns