-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows: py_binary launcher incorrectly escapes arguments #7958
Labels
area-Windows
Windows-specific issues and feature requests
P2
We'll consider working on this in future. (Assignee optional)
team-OSS
Issues for the Bazel OSS team: installation, release processBazel packaging, website
type: bug
Comments
laszlocsomor
added
bazel 1.0
P2
We'll consider working on this in future. (Assignee optional)
area-Windows
Windows-specific issues and feature requests
type: bug
labels
Apr 5, 2019
laszlocsomor
added a commit
to laszlocsomor/bazel
that referenced
this issue
Apr 8, 2019
See bazelbuild#7958 RELNOTES[NEW]: Windows, Python: the --incompatible_windows_escape_python_args flag (false by default) builds py_binary and py_test targets with correct command line argument escaping.
laszlocsomor
added a commit
to laszlocsomor/bazel
that referenced
this issue
Apr 8, 2019
See bazelbuild#7958 RELNOTES[NEW]: Windows, Python: the --incompatible_windows_escape_python_args flag (false by default) builds py_binary and py_test targets with correct command line argument escaping. Change-Id: I789f9370e2cf59fa1a179716ca1c6ad80e1d583e
This was referenced Apr 8, 2019
bazel-io
pushed a commit
that referenced
this issue
Apr 9, 2019
Incompatible flag: #7974 See #7958 RELNOTES[NEW]: Windows, Python: the --incompatible_windows_escape_python_args flag (false by default) builds py_binary and py_test targets with correct command line argument escaping. Change-Id: I789f9370e2cf59fa1a179716ca1c6ad80e1d583e Closes #7973. Change-Id: I789f9370e2cf59fa1a179716ca1c6ad80e1d583e PiperOrigin-RevId: 242628695
laszlocsomor
added a commit
to laszlocsomor/bazel
that referenced
this issue
May 10, 2019
Follow-up to PR bazelbuild#7973 Copy the --incompatible_windows_escape_python_args value also to the host config options. Incompatible flag: bazelbuild#7974 See bazelbuild#7958
bazel-io
pushed a commit
that referenced
this issue
May 10, 2019
aehlig
pushed a commit
that referenced
this issue
May 13, 2019
aehlig
pushed a commit
that referenced
this issue
May 17, 2019
aehlig
pushed a commit
that referenced
this issue
May 17, 2019
aehlig
pushed a commit
that referenced
this issue
May 20, 2019
aehlig
pushed a commit
that referenced
this issue
May 21, 2019
aehlig
pushed a commit
that referenced
this issue
May 22, 2019
aehlig
pushed a commit
that referenced
this issue
May 23, 2019
aehlig
pushed a commit
that referenced
this issue
May 23, 2019
aehlig
pushed a commit
that referenced
this issue
May 24, 2019
irengrig
pushed a commit
to irengrig/bazel
that referenced
this issue
Jun 18, 2019
Follow-up to PR bazelbuild#7973 Copy the --incompatible_windows_escape_python_args value also to the host config options. Incompatible flag: bazelbuild#7974 See bazelbuild#7958 Closes bazelbuild#8289. PiperOrigin-RevId: 247596101
Fixed in Bazel 0.27 |
philwo
added
the
team-OSS
Issues for the Bazel OSS team: installation, release processBazel packaging, website
label
Jun 15, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area-Windows
Windows-specific issues and feature requests
P2
We'll consider working on this in future. (Assignee optional)
team-OSS
Issues for the Bazel OSS team: installation, release processBazel packaging, website
type: bug
Description of the problem / feature request:
On Windows, py_binary.args and py_test.args are not Bash-tokenized and not escaped properly.
This bug is similar to #7072.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
BUILD
:testargs.py
:Actual (buggy) output:
Desired output:
What operating system are you running Bazel on?
windows 10
What's the output of
bazel info release
?release 0.24.1
The text was updated successfully, but these errors were encountered: