On Sat, Oct 23, 2010 at 2:20 PM, Antoine Pitrou solip...@pitrou.net wrote:
You mean: actively feeling responsible for it? I guess nobody - as for
many other modules in the standard library.
Or do you mean: who is willing to work on it, in principle?
Both. Originally the module is/was meant
On Sat, Oct 23, 2010 at 2:10 PM, Martin v. Löwis mar...@v.loewis.de wrote:
Who is doing multiprocessing maintenance these days? I thought Ask
Solem had been given commit privs for that, but I haven't seen any
activity from him; and Jesse is, mostly, absent. Is anyone working on
the
On Mon, 25 Oct 2010 10:01:43 -0400
Jesse Noller jnol...@gmail.com wrote:
On Sat, Oct 23, 2010 at 2:10 PM, Martin v. Löwis mar...@v.loewis.de wrote:
Who is doing multiprocessing maintenance these days? I thought Ask
Solem had been given commit privs for that, but I haven't seen any
activity
On Mon, Oct 25, 2010 at 7:19 PM, Antoine Pitrou solip...@pitrou.net wrote:
On Mon, 25 Oct 2010 10:01:43 -0400
Jesse Noller jnol...@gmail.com wrote:
On Sat, Oct 23, 2010 at 2:10 PM, Martin v. Löwis mar...@v.loewis.de
wrote:
Who is doing multiprocessing maintenance these days? I thought Ask
On Oct 23, 2010, at 8:10 PM, Martin v. Löwis wrote:
Who is doing multiprocessing maintenance these days? I thought Ask
Solem had been given commit privs for that, but I haven't seen any
activity from him; and Jesse is, mostly, absent. Is anyone working on
the multiprocessing issues?
(no,
If you have anything you want me to look at please forward it,
and if you already did then don't be afraid to nag me.
Please keep the release schedule in mind. After 3.2b1, no new
features can be accepted (until after the 3.2 release). So
there might be some urgency for some of the patches.
Who is doing multiprocessing maintenance these days? I thought Ask
Solem had been given commit privs for that, but I haven't seen any
activity from him; and Jesse is, mostly, absent. Is anyone working on
the multiprocessing issues?
(no, I'm not planning to address them :-))
You mean:
You mean: actively feeling responsible for it? I guess nobody - as for
many other modules in the standard library.
Or do you mean: who is willing to work on it, in principle?
Both. Originally the module is/was meant to be officially maintained by
Jesse, as far as I understand. But bugs
Both. Originally the module is/was meant to be officially maintained by
Jesse, as far as I understand. But bugs filed against multiprocessing
have been lingering in the tracker for quite a long time.
I personally think we should treat these reports in the same way as all
other lingering
