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

Pants

There isn't currently an equivalent of managed_jar_dependencies for python, correct?

if you only have one binary, transitively pinning your dependencies should be equivalent

<@U051221NF>: is it a known issue that some args are ignored?

```./pants bundle --bundle-jvm-archive=zip ./examples/src/java/org/pantsbuild/example/annotation/main```

```./pants bundle --jvm-bundle-archive=zip ./examples/src/java/org/pantsbuild/example/annotation/main```

latter succeeds silently, but ignores the argument

```./pants bundle --jvm-asdjkgsdk=zip ./examples/src/java/org/pantsbuild/example/annotation/main```

<https://github.com/pantsbuild/pants/issues/2254>

Is there  a way to "override"/shade/vendor (not sure which is the right word) a single module or file?  I'm trying to get requests to trust a corporate CA, whcih feels like it's probably something people have run into before <https://github.com/kennethreitz/requests/blob/master/requests/certs.py>

would it work if you released a unique version of the lib and then pinned to that version?

iirc, there’s an environment variable you can also use to control that outside of the code

Yeah fork/vendor would work, but I was trying to avoid that (vendoring is frowned upon and we don't actually have an internal PyPi)

My worry with the env variable is that I don't want to be responsible for setting it in a way that is truthful on multiple linux distros and OSX

how would you ensure the same via code modification?

My hypothetical hacky code was to read the requests bundled CA bundle and append to it

<@U06A03HV1>: yeah, that is the biggest weakness of the options system right now, I think.

<@U051221NF>: <@U0AALHEDR> volunteered to work on it... any suggestions?

would enforcing the full spelling of all options help in this case?

<@U0AALHEDR>: make sure you read through the issue description: <https://github.com/pantsbuild/pants/issues/2254>

sounds like it has something to do with not evaluating scopes that aren't used

```[tw-mbp-yic pants (silent_arg_fix)]$ ./pants resolve.ivy --jvm-options='123' options --no-colors | grep "123"
INFO] Detected git repository at /Users/yic/workspace/pants on branch silent_arg_fix
jvm.options = ['-Xmx1g', '-XX:MaxPermSize=256m', '123'] (from FLAG)```

I see. ‘123’ gets mapped to global option instead of inside of the scope

FWIW I think I'm going to "vendor" Certifi and maintain my own bundle, which is sucky, but at least sucky in a straightforward and not magical way