New submission from Pascal Chambon :
I feel the description of the subprocess.popen semantics is a little
incomplete/confusing to me, on some points, eg. :
- what does the "shell" argument do on windows, exactly ? The beginning
of the description states that nothing changes (createPr
New submission from Pascal Chambon :
Hello
A minor detail in optparse documentation :
"If optparse‘s default error-handling behaviour does not suit your
needs, you’ll need to subclass OptionParser and override its exit()
and/or error() methods."
-> the links put on exit() and erro
New submission from Pascal Chambon :
It seems that the "flock" wrapped by the fcntl module is the one
descriebd in "flock(2)", not "flock(3)" (just in case this might confuse
people...)
Quote :
"""
fcntl.flock(fd, op)
Perform the lock operation op
New submission from Pascal Chambon :
Hello
I once was rather confused, because nothing in the sys and os modules
mentionned the behaviours that the exit() and _exit() functions were
supposed to have when called inside a non-main thread.
I've eventually found in multithreading-related docs
Pascal Chambon added the comment:
I guess we all agree on the fact that a renaming of the API would be
highly disproportionate ;-)
A simple line of warning in the doc, next to the daemonic-related
methods, should be sufficient to prevent people like me from wondering
weird stuffs for hours
Pascal Chambon added the comment:
I agree that for someone who discovers the multiprocessing api as a
"generalization" of the threading api, there won't be problems ;
I'm just worried about those (like me) who will see "daemonic" as coming
from unix processes, a
New submission from Pascal Chambon :
"Usually, daemon processes are processes which got disconnected from
their parent process, and work in the background, often under a
different user identity.
The multiprocessing module has the concept of "daemon" too, but this
time in r
Pascal Chambon added the comment:
Thansk a lot for reviewing the problem
Indeed, "p.wait()" seems to do the trick in this case.
Is there any global way to avoid such pipe problems ? I mean, in any
case, one end of each pipe has to be closed before the other end, so
such errors m
New submission from Pascal Chambon <[EMAIL PROTECTED]>:
I've created on my desktop a file flooder.py containing just the following:
##
import sys, os
progress=open(r"C:\Users\v-pascha\Desktop\STDERR.txt","w")
for i in range(101):
print str(i)*2
101 - 109 of 109 matches
Mail list logo
