>
> To expand on that just a bit, the form of sharing that you get when you
> fork() but you don't exec() is very difficult to use correctly (I think
> it's an open question whether it's *possible* to use correctly in a Python
> program).
>
> The argument here is similar to the argument against sha
On 11:19 am, ita...@itamarst.org wrote:
On 10/23/2013 12:50 PM, Phil Mayers wrote:
This is a multiprocessing bug IMHO.
This issue with multiprocessing appears in other places too. E.g. if
you're using stdlib logging, child processes will try to rotate the
parent process logs.
Basically mu
On 10/23/2013 12:50 PM, Phil Mayers wrote:
This is a multiprocessing bug IMHO.
This issue with multiprocessing appears in other places too. E.g. if
you're using stdlib logging, child processes will try to rotate the
parent process logs.
Basically multiprocessing on Unix is utterly broken a
> > 2. Arrange for the epoll object (or FD) to be closed after fork, but
> > before exec, so that the child process can't fiddle with it
>
> See also:
>
> http://bugs.python.org/issue8713
>
> ...which suggests Python 3.4 added fork+exec support to multiprocessing.
> On Unix and older Python versi
>
> On 03:46 pm, grindi...@gmail.com wrote:
> >Hi everybody
> >
> >I a came across a surprising problem when using the epoll based
> >reactor.
> >(ticket here https://twistedmatrix.com/trac/ticket/6796)
> >
> >As you can see on the ticket, the epoll object seems to share some
> >state
> >even after
On 03:46 pm, grindi...@gmail.com wrote:
Hi everybody
I a came across a surprising problem when using the epoll based
reactor.
(ticket here https://twistedmatrix.com/trac/ticket/6796)
As you can see on the ticket, the epoll object seems to share some
state
even after fork.
[snip]
- Using s
On 23/10/13 17:39, Phil Mayers wrote:
2. Arrange for the epoll object (or FD) to be closed after fork, but
before exec, so that the child process can't fiddle with it
See also:
http://bugs.python.org/issue8713
...which suggests Python 3.4 added fork+exec support to multiprocessing.
On Uni
Hi,
this is funny, I am also working in this area currently.
Though I use spawnProcess for various reasons, not multiprocessing - which is
also the recommendation on the ticket. And it makes sense.
Nevertheless I'd be interested what happens if you try that on a kqueue-reactor
OS .. ideally Fr
On 23/10/13 16:46, Flint wrote:
Hi everybody
I a came across a surprising problem when using the epoll based reactor.
(ticket here https://twistedmatrix.com/trac/ticket/6796)
As you can see on the ticket, the epoll object seems to share some state
even after fork.
Which means even after having
