[msys2-runtime] arguments mangled when passed to cygwin executables
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 240
- Forks
- 60
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 1
Description
Same problem with Python2 and Python3
import subprocess;print(subprocess.check_output(['echo', '--foo="bar"', '--quux="baz"']).decode())
Prints --foo=\bar" --quux="baz" instead of --foo="bar" --quux="baz"
edit: minimal example ['echo', '"']
This breaks some meson builds when perl scripts are called. For example pango with help2man.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Python subprocess examples, including the minimal ['echo', '"'] case, and compare the output from cygwin executables. Investigate the MSYS2 runtime argument-passing path and verify the fix against the quoted arguments that currently break Meson builds involving Perl, such as pango with help2man.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, perl, python
- Domain
- build-system, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100