On 09/02/2017 12:19 PM, Zac Medico wrote: > On 09/02/2017 10:46 AM, Michał Górny wrote: >> dev-python/pycparser-2.18+ exposes a design flaw in dev-python/ply that >> makes it unable to work with -OO code. Remove the optimizations from >> Portage shebangs to prevent triggering the issue until we find a proper >> solution for it. >> >> Bug: https://bugs.gentoo.org/628386 >> --- >> bin/clean_locks | 2 +- >> bin/dispatch-conf | 2 +- >> bin/ebuild | 2 +- >> bin/emaint | 2 +- >> bin/env-update | 2 +- >> bin/portageq | 2 +- >> tabcheck.py | 2 +- >> 7 files changed, 7 insertions(+), 7 deletions(-) >> >> diff --git a/bin/clean_locks b/bin/clean_locks >> index 13af06197..fb245972f 100755 >> --- a/bin/clean_locks >> +++ b/bin/clean_locks >> @@ -1,4 +1,4 @@ >> -#!/usr/bin/python -bO >> +#!/usr/bin/python -b > > The diff shows -O, but the commit messages says -OO, so which one is it > really? > > Are we sure that it's worth it to load all of the __doc__ strings into > memory, given that we have alternative implementations for everything > that pycrypto provides?
Seems that we inadvertently dropped -O from the emerge shebang during some refactoring here: https://gitweb.gentoo.org/proj/portage.git/commit/?id=941dc5b26301075545e5fb3580f5d72c5f78c3cd -- Thanks, Zac
