https://pantsbuild.org/ logo
#pex
Title
# pex
e

enough-analyst-54434

10/20/2019, 10:12 PM
The idea of vendoring pip in pex to gain some pip features came up recently. I've started an issue here to discuss the idea: https://github.com/pantsbuild/pex/issues/781 @rough-minister-58256, @hundreds-father-404, @dry-analyst-73584, @happy-kitchen-89482 and others interested, I'd appreciate your considerations here. There is some care needed to keep built pexes small (we shouldn't need all of pip inside every built PEX for runtime use), but this may be otherwise sane. I do worry I'm missing problems here and counting on you all to spot them. Thanks in advance for your brain power.
📝 1
👌 1
👍 1
h

happy-kitchen-89482

10/22/2019, 5:53 PM
As my old office mate used to say: features are an asset, code is a liability. So if we can get more features for less code, that's a win in my book.
👍 1
We also get: 1) Greater consistency with pip, which may smooth the upgrade path to pex. And 2) At least one feature we know people currently want, namely support for resolving from a VCS.