-
-
Notifications
You must be signed in to change notification settings - Fork 254
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
Unable to execute pex utility on Windows #259
Comments
pex does not currently claim windows support. however, there have been a handful of recent PRs from the Buck team that have moved the needle to the point that some folks are making this work with modifications - see: #230 ultimately, windows support is something that the primary developers of pex do not have a need for or interest in (we are all mostly UNIX shops). if a reliable owner can be established to implement and maintain this functionality tho (including setup of AppVeyor for CI on windows, etc), we'd be amenable to that. it just hasn't materialized yet. |
@kwlzn i've landed on this issue from different perspective - would linux-built |
@nfx - almost certainly not. Known to not work is the file locking code Pex uses to keep its cache parallel-process safe. #1157 attempted to address this particular issue, but you might read there for more on where I stand with adding Windows support. In short, Pex does not support Windows and never has. PEXes have worked on Windows at various periods of time in the past, but by luck. Without green CI on a Windows machine I cannot in good faith support Windows Pex users. No one has had the time to get Pex working on Windows + CI setup to ensure no backslide as of yet. I did put in alot of work around a year ago but never completed. I am picking that work back up presently, but its likely to take a while - I only work on this part time. |
I don't see any mention of Windows in the docs, so perhaps
pex
simply doesn't support Windows, but I get the following errors when trying to do a simple install and run ofpex
on Windows 10.I even tried using the
--no-binary
flag forpip
, but it resulted in the same error:Before I went trying to investigate this too far, I wanted to check to see if Windows is really a supported platform to begin with.
The text was updated successfully, but these errors were encountered: