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

Pants

<https://github.com/python/cpython/blob/a6431f2c8cf4783c2fd522b2f6ee04c3c204237f/Lib/sysconfig.py#L75>

a couple months ago I got like 90% of the way to bazel building its own version of python2.7 from source

at the time, I got hung up on how to handle the standard library

and also realized that what I was doing was completely insane

wow, that *is* a setuptools bug, isn’t it

<https://github.com/pantsbuild/pex/blob/2fc3f73dcc8263edc965bb95e593787037207b64/pex/pex_builder.py#L288> &lt;— is `add_dist_location()` supposed to actually do something with that `name` parameter? It looks like it ignores it

`DistributionHelper.distribution_from_path` takes a name parameter; I suspect it should just be passed along there

I’m currently looking for a way to work with python wheels that have incorrect filenames

like `&lt;packagename&gt;.whl` instead of `&lt;packagename&gt;-1.2.3-py2-py3-none-any.whl`

I’m not sure if this will actually accomplish it

<@U0EB5B0UV>: <https://github.com/benley/bazel_rules_pex/pull/12>

Python always leaves you feeling dirty somehow

we ought to try to get mac builds working on travis :slightly_smiling_face:

You know what would be cool? If pex could look inside other pex files to find prebuilt dependencies

I don’t think it would be difficult to implement that

that lets you combine the environments of multiple pexes at runtime

I was thinking of it for building new pexes by pulling deps out of existing ones

It would be great for bazel, I think - have each pex_library be built as an actual pex, and downstream dependents inherit those contents at build time

I could probably fake that with some clever shims, but it would be slower

<@U0EB5B0UV>:  Have you chatted with anyone in Bazel about supporting Wheels &amp; Eggs in `python_library`?  It seems like there was a lot of contention around the idea of `pex_library` when this came up before

The main thing that’s missing from bazel’s builtin python support is the ability to build deployable zip-executables