Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
V2 `./pants test.pytest` selects interpreter based off of compatibility constraints #7679
Currently the V2 task will always use the current interpreter to run Pytest, even if the targets have different requirements. Instead, we must support choosing the interpreter for the subprocess based on the targets' compatibility (which falls back to global compatibility if missing).
Note that we let Pex do the intepreter resolution for us to simplify the Pants code. All we have to do is pass the interpreter constraints to PEX, along with exposing the
NB: You can run a pex with an interpreter of your choice:
referenced this pull request
May 8, 2019
The source code is complete, modulo requested changes.
This is still missing test code. Stu and I talked a little over Slack about this—not quite sure what is meaningful to test here, e.g. integration test vs unit test. I have to get going for the day but any ideas on what to test would be much appreciated, as I've never done testing with V2 before.
stuhood left a comment •
Thanks, looks good.
As to testing this, a few tools for the toolbelt: