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