Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add back interpreter_constraints field to pex_binary and python_awslambda #11979

Merged
merged 2 commits into from Apr 29, 2021

Conversation

Eric-Arellano
Copy link
Contributor

[ci skip-rust]

…11977)

This should not have been deprecated in 2.2.x - that was a mistake. Even though `pex_binary` no longer has a `sources` field, it is still sensible to want to change the interpreter constraints for a binary. For example, it is totally valid to have a `pex_binary` with no first party code and only 3rd party reqs, and to want to set the constraints for that.

[ci skip-rust]
[ci skip-build-wheels]
@Eric-Arellano Eric-Arellano changed the title Add back interpreter_constraints field to pex_binary (Cherry-pick of #11977) Add back interpreter_constraints field to pex_binary and python_awslambda Apr 29, 2021
# Rust tests and lints will be skipped. Delete if not intended.
[ci skip-rust]

# Building wheels and fs_util will be skipped. Delete if not intended.
[ci skip-build-wheels]
@Eric-Arellano
Copy link
Contributor Author

This is no longer a cherry-pick - I realized I needed to add back interpreter_constraints to python_awslambda too.

@Eric-Arellano Eric-Arellano merged commit 54860a0 into pantsbuild:2.4.x Apr 29, 2021
@Eric-Arellano Eric-Arellano deleted the cp-pex-24 branch April 29, 2021 19:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants