1 |
On 11/23/2013 02:45 PM, james N. wrote: |
2 |
> On 11/22/2013 07:31 PM, Alecks Gates wrote: |
3 |
> |
4 |
>> > |
5 |
>> > What kernel are you running and/or what kernel did you build python2.7 |
6 |
>> > with? I would try remerging dev-lang/python:2.7 |
7 |
>> > |
8 |
>> > Possibly relevant: |
9 |
>> > http://bugs.python.org/issue8326 |
10 |
|
11 |
Interesting thread, thanks. My gut feeling was that the kernel would have no |
12 |
effect on python packages, but now I need to rethink that. |
13 |
|
14 |
> I ran python-updater like Walt suggested, no help. |
15 |
> Then I rebuilt dev-lang/python:2.7 still didn't help. |
16 |
> |
17 |
> python-2.7 was built against gentoo-sources-3.11.0 which is my current kernel. |
18 |
|
19 |
My kernel-tinkering experience may have nothing to do with your python bug, |
20 |
but I'll mention it anyway because I love the sound of my own key-clicks :) |
21 |
|
22 |
The "0" at the end of 3.11.0 means that kernel has had very little testing |
23 |
and may well contain many new bugs. If you don't want to spend your time |
24 |
bisecting and reporting kernel bugs you should probably wait at least until |
25 |
that "0" increments to around "3" before using it. |
26 |
|
27 |
Given the ubuntu bug report I'd suggest trying a kernel in the 3.10.* range |
28 |
as an experiment. |