if 1, you still have a problem, no? taken together, both 

pex_binary

 targets result in 

ansicolors + future

 being used. which will cause a failure w/ the multiplatform pex, regardless of having a dedicated lockfile for each platform

i think that this discussion is maybe not great for slack. but. if you have a binary that says

ansicolors + future

are needed on both platforms, and they aren’t available there, then… that’s just the status quo. it should fail, because PEX/pip don’t support it.