Please confirm the following
Describe the bug
Since #1586 the default builds are "release" (-g0 -Ofast -NDEBUG -s) or "debug" (-g3 -Og ...).
However, all Linux distributions and probably others such as homebrew and macports, don't build like this at all.
The standard behaviour for Linux is to build with something along the lines of -g -O2 and then split the debug symbols into separate packages, so out of the box the binaries are optimised enough and debug symbols that mostly work are easily available.
The usual way we do this is by setting CFLAGS to the flags we want, and expecting packages to follow them. Whilst I respect your desire for the binary wheels you ship to be built in fully optimised, is there a way to opt out of this behaviour?
To Reproduce
Build yarl, expect debug symbols in the binary.
Expected behavior
Yarl will respect CFLAGS/LDFLAGS and not forcibly add its own flags.
Logs/tracebacks
Python Version
multidict Version
$ python -m pip show multidict
propcache Version
$ python -m pip show propcache
yarl Version
$ python -m pip show yarl
OS
Linux
Additional context
No response
Please confirm the following
vulnerability, to the best of my knowledge. (These must be shared by
submitting this report form instead, if
any hesitation exists.)
Describe the bug
Since #1586 the default builds are "release" (
-g0 -Ofast -NDEBUG -s) or "debug" (-g3 -Og ...).However, all Linux distributions and probably others such as homebrew and macports, don't build like this at all.
The standard behaviour for Linux is to build with something along the lines of
-g -O2and then split the debug symbols into separate packages, so out of the box the binaries are optimised enough and debug symbols that mostly work are easily available.The usual way we do this is by setting
CFLAGSto the flags we want, and expecting packages to follow them. Whilst I respect your desire for the binary wheels you ship to be built in fully optimised, is there a way to opt out of this behaviour?To Reproduce
Build yarl, expect debug symbols in the binary.
Expected behavior
Yarl will respect CFLAGS/LDFLAGS and not forcibly add its own flags.
Logs/tracebacks
Python Version
$ python --versionmultidict Version
$ python -m pip show multidictpropcache Version
$ python -m pip show propcacheyarl Version
$ python -m pip show yarlOS
Linux
Additional context
No response