This is still somewhat experimental, but I now hav...
# development
a
This is still somewhat experimental, but I now have a branch against 2.14 where you can build a standalone Pants binary using PyOxidizer: https://github.com/pantsbuild/pants/pull/16414 I believe everything in here should work as intended, and it successfully runs against our example repos. I haven’t looked at out-of-repo plugins just yet, and that’s likely to be somewhat gnarly, but if there’s other stuff that doesn’t work, I’d love to hear about it!
🤯 4
❤️ 1
w
Definitely gonna try this tonight! Super pumped
❤️ 2
Also, I like that my first Pants plugin is being used here 🙂
💯 2
h
Also, I like that my first Pants plugin is being used here 🙂
I thought the same thing 🥰
a
Yes! It made a lot of the work very easy!
❤️ 2
w
@ancient-vegetable-10556 What is
src/python/pants:pants-packaged
? Were you able to bypass needing to use wheels or did you still use a wheel? ie. https://github.com/sureshjoshi/pants-plugins/issues/11
a
pants-packaged
is the Pants distribution wheel
👍 1
so it ends up being a binary distribution based on the existing packages
w
Hmm "Bad CPU type in executable"
I guess you're on an M1? I dropped the
triple
h
yeah, Chris and I are on M1s
w
No love for us ol' x86-timers
🙈 1
Alright, pretty pretty cool! I'm able to run vanilla pants stuff on my pants-plugins repo, but in-repo plugins aren't pulled in
❤️ 1
I get an error about not understanding what "experimental" is, but that's okay - this is fantastic for the 90% workflow!
Great work @ancient-vegetable-10556
❤️ 1
h
I'm weeping for joy
Almost, but not quite, literally
🤣 1
a
@wide-midnight-78598 thanks for noticing — the triple wasn’t even necessary on my M1 once I eventually got things working. I suspect plugins will be an interesting process, depending on what import machinery still exists in PyOxidized binaries.
👍 2
(I am 90% certain that
zipimport
will work, if we can put together an appropriate archive)