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 if 2, it's solved. the dedicated lockfile for the

pex_binary

#1 w/ only

ansicolor

can be multiplatform just fine because the lockfile == exactly what is used by the binary. That works, but is a pain to maintain 2 lockfiles