If anyone can reproduce <https://github.com/pantsb...
# development
b
If anyone can reproduce https://github.com/pantsbuild/pants/issues/16099 locally and has a chunk of time to help me pair I'd really appreciate it ❤️
1
f
If you still need someone to pair program with on the issue, let me know, I have some time although I’m probably closer to the proverbial rubber duck than knowledgeable about the Pants Python stack.
b
Can you reproduce the PEX issue?!
"no module named 'pex'"
f
I’m still getting the error about the debugpy.lock being missing from the Pants venv.
weirdly the entire venv at the path is missing
and I wiped out ~/.cache/pants and .pants.d
b
Kill pantsd?
f
that was it. 🤦
😅 1
now I get:
Copy code
pex.environment.ResolveError: A distribution for debugpy could not be resolved for /Users/tdyas/.pyenv/versions/3.8.12/bin/python3.8.
Found 1 distribution for debugpy that do not apply:
1.) The wheel tags for debugpy 1.6.0 are cp37-cp37m-macosx_10_15_x86_64 which do not match the supported tags of /Users/tdyas/.pyenv/versions/3.8.12/bin/python3.8:
cp38-cp38-macosx_12_0_x86_64
... 1719 more ...
b
🙈 gahh There's a 3.8 tag in the lockfile
f
Putting aside fixing that tag, should I just switch my Python version to 3.9 or something else?
b
It looks like you're using 3.8, right?
Thats what I'm using, but yeah try that I suppose
b
I think the pants runner just goes from 3.6 up until it gets a match
Or wait looks like it goes down from 3.9 perhaps?
f
I also set
PYTHON=python3.9
in the env and
./pants
does look at that.
f
but elsewhere in that script it looks at
PYTHON_BIN_NAME
(which is set from
PYTHON
) to determine what version to use.
b
Might need to kill pantsd again?
f
already did that
b
🤷‍♂️
(jumping off for 30)
If you do smother out all the issues and see the specific one I'm trying to debug let me know 🙂
f
will do. had to work on other stuff so will try to get back to it tomorrow.
h
@bitter-ability-32190 is this thread still relevant, e.g. trying out the solution?
b
Yes, sadly
Doesn't seem to repro on my desktop 😫
h
alright, so 1) try to repro the bug, then 2) try out your fix, right?
b
Yup!
That should fix the import PEX issue. Not sure how related it is to the secondary issue in the ticket 😔
PR merged, but leaving issue open
So to clarify @happy-family-315, this seems to have fixed both issues?!
h
@bitter-ability-32190 Yes, both issues seem to be fixed for now
❤️ 1