I configured
```interpreter_constraints = ["CPytho...
# generalh
high-yak-85899
11/13/2023, 11:07 PMI configured
Copy code
interpreter_constraints = ["CPython>=3.8,<=3.8.10"]pyenv3.8.16high-yak-85899
11/13/2023, 11:13 PMLooks like the source code just uses
interpreter_versions_universeb
broad-processor-92400
11/13/2023, 11:16 PMYeah, I think it's a "known" bug: https://github.com/pantsbuild/pants/pull/19462#discussion_r1264007907
Can you file an actual bug? Thanks!
h
high-yak-85899
11/13/2023, 11:23 PMhigh-yak-85899
11/13/2023, 11:23 PMAny tips on patching this locally? I know bazel has some mechanisms for patching things locally.
b
broad-processor-92400
11/13/2023, 11:26 PMThanks!
I don't know the best way.
I guess you could copy out the whole pyenv backend to a plugin, fix the problem (enough for you, anyway) and use that new backend instead of the built-in one. 🤷♂️
(Somewhat facitiously, another "patch" locally might be lifting your upper bound to support all 3.8 interpreters... but I can imagine that's not feasible 😄 )
h
high-yak-85899
11/13/2023, 11:29 PMYup, it's not. We have tickets for it, but there's lots of asyncio deprecations to account for and a few other things blocking that.
high-yak-85899
11/13/2023, 11:29 PMOn our roadmap for sure, though, since 3.8 is end of life
b
broad-processor-92400
11/13/2023, 11:29 PMyeah, I feel you. Good luck!
2 Views