This problem does not happen very often, but when it happen is only on system startup, and I couldn't reproduce by starting by hand. My startup script tries to initiate a lot of services in sequence (ruby, java, C and python), but does not do anything with stdio streams, at least not directly.
At first, I thought this could be related to this python issue: http://bugs.python.org/issue13146 but this does not relate with "can't initialize sys standard streams" error. I didn't have time, though, to update my python version and check this won't happen again. Robison On Tue, Sep 25, 2012 at 10:59 AM, Oscar Benjamin <oscar.j.benja...@gmail.com > wrote: > On 25 September 2012 14:56, Robison Santos <rwrsan...@gmail.com> wrote: > >> I'm using python3.2.1 >> on Enterprise Linux Server release 5.3 (Carthage). >> >> I'm starting my apps calling python3 file.py <params> >> >> I have a script that runs on system startup executing my python scripts. >> > > What happens if you just run the scripts from the shell after starting up? > > What arrangement does the startup script provide for the stdio streams? > > Oscar >
-- http://mail.python.org/mailman/listinfo/python-list
