Re: <https://github.com/pantsbuild/pants/issues/73...
# development
w
Re: https://github.com/pantsbuild/pants/issues/7369 Is there any value in looking at
pyoxy
for this? https://gregoryszorc.com/blog/2022/05/10/announcing-the-pyoxy-python-runner/ Basically pieces of PyOxidizer extracted out of the build process.
đź’Ż 1
Ha! I misread that the blog post came out March 10th, not this morning 🙂
w
yea, possibly relevant… @enough-analyst-54434 is likely going to be picking that issue up in the next few weeks.
i expect that we’ll continue to have a “setup”/`pants` script, and so we have flexibility as to the distribution model… one file vs two isn’t really a problem.
but it’s not clear to me how
pyoxy
would help with thirdparty dependencies… the benefit of pyoxidizer/pyembed from my perspective is embedding the artifacts as well. if you still needed to give
pyoxy
a yaml file with a PYTHONPATH containing a bunch of installed distributions, you’re reinventing a lot of machinery i think
w
I was primarily thinking of standalone python dists - because on my machine(s), I've definitely noted some quirks with how my py environments are or aren't picked up - also also if my python for pants is out of sync with what my project needs. I wasn't particularly thinking about the other aspects. I still think that, ideally, a single PyOxidizer'd (or whatever) binary would be the goal.
w
got it. yea, that wouldn’t be https://github.com/pantsbuild/pants/issues/7369 though… that would be as a way for Pants to provide its own python interpreters for user code
there has been some discussion of adding support for an optional private
pyenv
install… using
pyoxy
might be an alternative to that
đź‘Ť 2