In article <2542cf60-a193-4087-a1fe-1d60ee13c...@v25g2000yqk.googlegroups.com>,
lofic wrote:
>On 7 f=E9v, 17:00, a...@pythoncraft.com (Aahz) wrote:
>> In article <188bfb67-3334-4325-adfc-3fa4d28f0...@d27g2000yqn.googlegroups=
>.com>,
>> lofic =A0 wrote:
>>>
>>>Works fine on RHEL5/python 2.4.3
>>>
On 7 fév, 17:00, a...@pythoncraft.com (Aahz) wrote:
> In article
> <188bfb67-3334-4325-adfc-3fa4d28f0...@d27g2000yqn.googlegroups.com>,
>
> lofic wrote:
>
> >Works fine on RHEL5/python 2.4.3
> >Hangs on RHEL4/python 2.3.4
>
> Then use Python 2.4 -- surely you don't expect anyone to provide bugfi
In article <188bfb67-3334-4325-adfc-3fa4d28f0...@d27g2000yqn.googlegroups.com>,
lofic wrote:
>
>Works fine on RHEL5/python 2.4.3
>Hangs on RHEL4/python 2.3.4
Then use Python 2.4 -- surely you don't expect anyone to provide bugfixes
for a release that's several years old?
--
Aahz (a...@pythoncra
Hello,
I've seen many messages and bug reports on popen2 about pipes, buffer
size problems, sub-processes not properly closed, race conditions,
popen2 not being thread safe... But I still can't figure what applies
to my case.
This piece of code:
#!/usr/bin/python
import threading
import popen2
