pygradle
pygradle copied to clipboard
could not find compatible interpreter
I am working on a fork of pygradle on windows. trying to do a fat pex, i keep getting the error
Could not find compatible interpreter
i have been debugging this for days and i narrowed it down to this command line. I can paste this into a command prompt and get the same error. The problem is i can't figure out why.
C:\tmp\junit4200936403494470163\foo\build\venv\Scripts\python.exe C:\tmp\junit4200936403494470163\foo\build\venv\Scripts\pex.exe --no-pypi --cache-dir C:\tmp\junit4200936403494470163\foo\build\pex-cache --output-file C:\tmp\junit4200936403494470163\foo\build\deployable\bin\hello_world.py --repo C:\tmp\junit4200936403494470163\foo\build\wheel-cache --python-shebang C:\apps\Python\Python36-32\python.exe --entry-point foo.hello:main foo
Now i did find an article where someone says that if Pex doesn't have access to the internet this could happen, which the fact my developers don't have access to the internet is why i have had to rewrite large swaths of Pygradle and pivy (thus the fork). But this one is killing me. I know zero about pex, can anyone see something obvious as to why this isn't working? The only screwy thing i can see is that the pex-cache folder doesn't exist, but im not sure its supposed to when this command is executed.
I should also note, my development machines only have python 3.6, none of them have python 2 installed as we don't support python 2 here.
i should note, that when i put the -i <my artifactory server> command in this i get the expected SSL errors (we run an internal CA server that python doesnt recognize, but as i am reading the docs, the command shouldn't have to hit pypi, it should have everything it needs in the wheel-cache folder right?
I figured this out and hit a wall at the same time. First, the error was because it couldn't connect to the internet. I was able to get thru that and rewrite a few things to hard code our internal artifactory server. The wall, pex compiler doesn't work on windows 10 because you have to be an admin to create symlinks on win10.