Regression from pathconv changes
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 240
- Forks
- 60
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 1
Description
Previously msys2-runtime converted the path separator from : to ; when passing to a Windows program. Now, for some reason, this doesn't work:
$ A=.:../test python -c 'import os; print(os.environ["A"])'
.:../test
Though if it's the PATH variable it seems to work.
$ PATH=".:../test" /mingw64/bin/python -c 'import os; print(os.environ["PATH"])'
.;C:\Users\test
Output from an old version of runtime for reference:
$ A=.:../test python -c 'import os; print(os.environ["A"])'
.;..\test
This is probably why rebuilding texlive errors out, see https://github.com/msys2/MINGW-packages/pull/19921#issuecomment-1923454422.
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
Reproduce the reported commands with msys2-runtime, comparing conversion of A with the special handling of PATH and the old runtime output. Start by tracing the pathconv changes mentioned in the title; done means non-PATH environment values passed to Windows programs convert separators as they did previously, without breaking PATH behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100