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

Pants

sort of wondering if we shouldn’t vendor setuptools + packaging + wheel ourselves in pex..

we already do so with setuptools - ish and I just got burned by not doing so for packaging

Of course setuptools itself just unvendored packaging

I can't think of an argument against vendoring - except...

I think pex apis leak pkg_resources types

So we'd need buffer types then in the public apis to vendor properly

Well, I work for real tomorrow -&gt; thurs and leave friday so I'm just going to stick to working the current missing `packaging` issue in .bootstrap

Thanks for your help today Kris... hopefully last burn today.

pex 1.2.1 is released:
- <https://pypi.python.org/pypi/pex/1.2.1>
- <https://github.com/pantsbuild/pex/releases/tag/v1.2.1>

is that the right place to ask about a pex issue with pants 0.0.64 (in apache aurora 0.11.0)?

trying to understand this message: ```Exception message: Package SourcePackage(u'file:///home/tdyas/.cache/pants/plugins/lockfile-0.10.2.tar.gz') is not translateable by ChainedTranslator(EggTranslator, SourceTranslator)
```

-.txt

<@U0N6C2Q9F|tdyas> uploaded a file: <https://pantsbuild.slack.com/files/tdyas/F3WDTU0AU/-.txt|Untitled>

`sys` being `None` is a pretty low level weirdness - did you dig into that?

for context, I had set `PYTHON` to `/usr/bin/python2` (CentOS 7 system python)

running its repl, I'm able to `import sys` just fine

seems like it is trying to translate the lockfile module from .tar.gz to egg?

and if I run the python from within the pants bootstrap location (`/home/tdyas/.cache/pants/setup/bootstrap/pants.YgrO6x/install/bin/python2.7`), I'm still able to `import sys`

even made sure our local custom-built python was not on the PATH