I noticed that profile-guided optimisation and link-time optimisation have both been unconditionally disabled in Buster's Python 3.6 and 3.7 packages, though 3.5 in Stretch had them both enabled (on common platforms).
Can anyone tell me why this was done? I see nothing about this in debian/changelog and the indentation in debian/rules looks odd, so I'm wondering if it might even have been an unintentional change. It's these extra lines in debian/rules: with_pgo = with_lto = just before the ifeq ($(with_lto),yes) line. -M-
