> > Since it's thrown on os.fork(), I suspect cygwin is the culprit, but > > that's just my gut feeling. > > There have been some changes in the fork-semantics (?) AFAIKS > in the latest > snapshots. Also what heppens if you roll back to cygwin-1.3.18-1?
I didn't know about the possibility of rollback. Rolling back cygwin didn't help, but rolling back Python did! (From 2.2.2-4 to 2.2.2-1) /Marcus -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
