📦 Make release builds compile very optimized#1586
Merged
webknjaz merged 3 commits intoaio-libs:masterfrom Oct 28, 2025
Merged
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This patch improves the in-tree build backend to allow the end-users append
CFLAGSandLDFLAGSby setting respecitve environment variables.It additionally sets up default compiler flags to perform build with maximum optimization in release mode. And when line tracing is requested, the compiler and linker flags are configured to include as much information as possible for debugging and coverage tracking.
As a result, the C-extensions published to PyPI are going to be small while their development/testing environment variants will be big.
Are there changes in behavior for the user?
yarl's footprint is smaller, and it should run faster.
Checklist