Currently there are not many user-friendly docs, and I tried my best to figure out what is the minimal configuration to achieve this. Feedbacks are welcome!

https://github.com/lablup/example-self-contained-python-app/commit/f7db8e54bce4a4ea301d5ae2ec22f073896c2d1e I'm not sure why I must provide the absolute path of

science

executable, but this makes it portable with PATH.

I've been using this in prod for the same amount of time

it seems to work pretty well, but i found a strange issue while working with some entrypoints of pex binary targets.

__main__.py

and

main.py

are lost in the pex package.;; I haven't done anything special with them....

is there any special treatment done to

main.py

or

__main__.py

when building pex?

hmm... it was some strange behavior of dependency resolution when

___init___.py

has

from . import module

patterns. I have added an explicit import there and resolved the missing

main.py

issue.

I had to manually update the science binary versions and the indygreg release date to match the interpreter constraint, and now confirmed the built binary is executed in a fresh new Ubuntu VM.

The last issue remains here... is that the executable downloads the indygreg build even though it seems to already include one considering the file size! (~26MB)

ah, this is not a bug; accidentally my pex build size was similar to the indygreg build...

Please note that my plugin could also be causing some inconsistencies you're seeing. So, if there are errors you see, PEX is it's own thing, my plugin is an attempted hack of a wrapper, that works for simple cases. I'll be formalizing it in the next couple of months and maybe PR'ing into main, but not until we can have > 1 PEX fix, as that's a silly, lazy limitation by me