linkedin / linkedin/pygradle

could not find compatible interpreter

Open
#153 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
603
Forks
142
PR merge metrics
No merged PRs in 30d

Description

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the exact Windows command in the issue, then inspect how PEX selects compatible interpreters when using the specified Python 3.6 executable and offline cache paths. Done means the command creates the requested hello_world.py output without reporting that it cannot find a compatible interpreter.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.