1 |
On Fri, 2009-10-23 at 15:30 +0200, Fabian Groffen wrote: |
2 |
> On 23-10-2009 14:28:17 +0100, Alan Hourihane wrote: |
3 |
> > On Fri, 2009-10-23 at 15:14 +0200, Fabian Groffen wrote: |
4 |
> > > On 23-10-2009 11:00:14 +0200, Fabian Groffen wrote: |
5 |
> > > > On 23-10-2009 10:15:11 +0200, Markus Duft wrote: |
6 |
> > > > > it seems that the code using os.pipe() seems either broken or the |
7 |
> > > > > interix implementation of that python code is broken... whichever it is |
8 |
> > > > > - it's bad ... :( |
9 |
> > > > > |
10 |
> > > > > Could you (grobian), please add "Interix" to the existing white list for |
11 |
> > > > > openpty platforms? |
12 |
> > > > |
13 |
> > > > geez... Interix really sucks. Anyway, if you add it to 701, does it |
14 |
> > > > work then, or does it hang in that case? |
15 |
> > > |
16 |
> > > hmm that check in portage looks totally broken to me, and makes |
17 |
> > > sparc/solaris hang too... |
18 |
> > |
19 |
> > Which area is this as I've noticed FreeMiNT's emerging process takes |
20 |
> > much longer at the moment. |
21 |
> |
22 |
> usr/lib/portage/pym/portage/__init__.py |
23 |
> |
24 |
> look for openpty |
25 |
> |
26 |
> there is a bit of code to test whether this can work or not also |
27 |
> involving python 3.1 |
28 |
|
29 |
O.k. I'll take a look. |
30 |
|
31 |
> I also feel everything got slower |
32 |
|
33 |
It has, most definitely. On slower platforms this can be painful, but |
34 |
before it was actually quite snappy. |
35 |
|
36 |
Alan. |