Hello everybody,
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 :-))
On Sat, Oct 23, 2010 at 5:11 AM, Brett Cannon br...@python.org wrote:
On Fri, Oct 22, 2010 at 09:26, Georg Brandl g.bra...@gmx.net wrote:
Am 19.10.2010 17:24, schrieb P.J. Eby:
Well, my intention at least was that they should be documented and
released; it's the documenting part I didn't get
On Wed, 13 Oct 2010 17:50:49 -0500
Brian Curtin brian.cur...@gmail.com wrote:
[...]
I have a Server 2008 R2 x64 box with the full Visual Studio that I could add
to the buildbot fleet. It's a dual core with 4 GB of RAM, plenty of disk
space, and it runs 24/7.
The adventures of
Hello,
The first 3.2 beta is scheduled by Georg for November 13th.
What would you think of scheduling a bug week-end one week later, that
is on November 20th and 21st? We would need enough core developers to
be available on #python-dev.
Regards
Antoine.
Am 23.10.2010 19:08, schrieb Antoine Pitrou:
Hello,
The first 3.2 beta is scheduled by Georg for November 13th.
What would you think of scheduling a bug week-end one week later, that
is on November 20th and 21st? We would need enough core developers to
be available on #python-dev.
I'll
Am 22.10.2010 16:09, schrieb Benjamin Peterson:
2010/10/22 Dirkjan Ochtman dirk...@ochtman.nl:
On Fri, Oct 22, 2010 at 00:57, Benjamin Peterson benja...@python.org wrote:
In the interest of getting 3.1.3 and 2.7.1 out by next year, here's a
tentative release schedule:
November 13th - RC1
Issues stats:
open2494 (+32)
closed 19460 (+110)
total 21954 (+56)
The figures in parentheses look wrong. Last week, the stats said:
No: they just mean something different that you think.
+32 doesn't mean that there are now 32 more open issues than
last week, but that 32 issue
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
2010/10/23 Martin v. Löwis mar...@v.loewis.de:
I'm worried about build identification. Either the switchover happens
before RC1, or after Final. I expect significant breakage from the
Mercurial switchover, so that should all be figured out before or after
the release.
I hope that can be well
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
I will also do any future 2.6 release from svn. It does mean that patches for
those release need to make it into svn. I propose that only the RM have commit
to the svn branches after the switch.
Sent from my digital lollipop.
On Oct 23, 2010, at 2:03 PM, Martin v. Löwis mar...@v.loewis.de
Am 23.10.2010 20:56, schrieb Barry Warsaw:
I will also do any future 2.6 release from svn. It does mean that
patches for those release need to make it into svn. I propose that
only the RM have commit to the svn branches after the switch.
This is also my thinking. I would like to see a
Hello.
I'm a student under 18 years, who really like programming in python. Few
days ago I've found Google Code-In
contesthttp://code.google.com/opensource/gci/2010-11/faqs.html,
and I'm seriously considering it as a good opportunity do get more confident
with Python. Although I've fixed a pair of
14 matches
Mail list logo
