You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Soon, we will fix platforms in V2 to override whatever the --interpreter-constraint flag would have been that we normally pass to Pex. As explained in pex-tool/pex#957, it does not make sense to specify both flags.
But, this means that it is possible, for example, for the transitive closure of a python_binary to have Python 2.7 interpreter constraints, but a platform of linux-x86_64-cp-37-cp37m. We would end up building a Pex compatible with Py37, even though the code would normally use Py27. Arguably, it would be better to warn/error with a nice error message here.
Implementation wise, we could leverage pkg_resources:
Soon, we will fix
platforms
in V2 to override whatever the--interpreter-constraint
flag would have been that we normally pass to Pex. As explained in pex-tool/pex#957, it does not make sense to specify both flags.But, this means that it is possible, for example, for the transitive closure of a
python_binary
to have Python 2.7 interpreter constraints, but a platform oflinux-x86_64-cp-37-cp37m
. We would end up building a Pex compatible with Py37, even though the code would normally use Py27. Arguably, it would be better to warn/error with a nice error message here.Implementation wise, we could leverage
pkg_resources
:The text was updated successfully, but these errors were encountered: