Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

well, typically the pants venv would be a temporary artifact within a git repo

that can rebuild itself etc on version bumps, plugin changes, etc

so the version of pants would travel with the code

I think I can still support that pretty easily unless it tries to modify itself in place

alright, I'll probably just try hacking at it and see if I run into a wall

and then either give up or try something else :slightly_smiling_face:

you could always package pants up as a pex (which is an alternative to venv)

```[illuminati pants (master)]$ pex pantsbuild.pants -e pants.bin.pants_exe:main -o /tmp/pants.pex
[illuminati pants (master)]$ /tmp/pants.pex
No goals specified.
Use `pants goals` to list goals.
Use `pants help` to get help.```

I might try that if this first attempt doesn't work

this gives you effectively an ‘immutable zipped venv executable'

is pants itself aware that it's in a pex? as in, does it have a special code path for running in that mode?

or is pex just taking care of bundling for me?

no special code path, it should just all work

but depending on the pants.ini in the repo you’re running pants in it may be missing plugins, etc

this is where the self-bootstrapping venv is handy

I think the nix version will end up being somewhat like the pex but not quite identical, and we'll miss out on special handling for the ini but can handle that in a slightly different way that hopefully won't be too inferior

will keep you posted on progress if you're interested

sure - always good to understand alternative usage and deployment patterns

cool :slightly_smiling_face: (watch me fail miserably in 5 minutes and give up :P)

does anyone know how to add extra JVM flags to the ivy step of pants? i'm trying to do add these flags: "-Djavax.net.ssl.keyStore=/path/to/file.jks", "-Djavax.net.ssl.keyStorePassword=abcdefg"

i've tried adding it to my pants.ini under [DEFAULT] jvm_options as well as [ivy] jvm_options, and neither work

i notice that pants/ivy/ivy.py the method Ivy.execute has a parameter for jvm_options, but the way ivy/bootstrapper.py calls it in _bootstrap_ivy_classpath , we don't pass in any jvm_options value