Re: [Python-Dev] Promoting PCbuild8 (Was: Python 2.5 performance)

2006-10-17 Thread Martin v. Löwis
Kristján V. Jónsson schrieb: > Okay, a buildbot then doesn't sound quite that scary. Any info > somewhere on how to set one up on a windows box? Sure. See http://wiki.python.org/moin/BuildbotOnWindows Feel free to make changes if you find the instructions need to be enhanced. > I Also wasn't s

[Python-Dev] who is interested on being on a python-dev panel at PyCon?

2006-10-17 Thread Brett Cannon
For the past couple years there has been the suggestion of having a panel discussion made up of core developers at PyCon.  Basically it would provide a way for the community to find how we do things, where we are going, our views, etc. I have finally decided to step forward and try to organize such

Re: [Python-Dev] svn.python.org down

2006-10-17 Thread skip
Anthony> Ah - the svn-apache server was down. I've restarted it. We Anthony> should probably put some monitoring/restarting in place for Anthony> those servers - if someone wants to volunteer a script I'll add Anthony> it to cron, or I'll write it myself when I get a chance. Is th

Re: [Python-Dev] svn.python.org down

2006-10-17 Thread Paul Moore
On 10/17/06, Anthony Baxter <[EMAIL PROTECTED]> wrote: > Ah - the svn-apache server was down. I've restarted it. We should probably put > some monitoring/restarting in place for those servers - if someone wants to > volunteer a script I'll add it to cron, or I'll write it myself when I get a > chan

Re: [Python-Dev] svn.python.org down

2006-10-17 Thread Anthony Baxter
Ah - the svn-apache server was down. I've restarted it. We should probably put some monitoring/restarting in place for those servers - if someone wants to volunteer a script I'll add it to cron, or I'll write it myself when I get a chance. (I was testing with svn+ssh, it was the http version th

Re: [Python-Dev] svn.python.org down

2006-10-17 Thread Paul Moore
On 10/17/06, Anthony Baxter <[EMAIL PROTECTED]> wrote: > On Wednesday 18 October 2006 00:59, Grig Gheorghiu wrote: > > FYI -- can't do svn checkouts/updates from the trunk at this point. > > > > starting svn operation > > svn update --revision HEAD > > in dir /home/twistbot/pybot/trunk.gheorghiu-x

Re: [Python-Dev] svn.python.org down

2006-10-17 Thread Grig Gheorghiu
On 10/17/06, Anthony Baxter <[EMAIL PROTECTED]> wrote: > On Wednesday 18 October 2006 00:59, Grig Gheorghiu wrote: > > FYI -- can't do svn checkouts/updates from the trunk at this point. > > > > starting svn operation > > svn update --revision HEAD > > in dir /home/twistbot/pybot/trunk.gheorghiu-x

Re: [Python-Dev] svn.python.org down

2006-10-17 Thread Anthony Baxter
On Wednesday 18 October 2006 00:59, Grig Gheorghiu wrote: > FYI -- can't do svn checkouts/updates from the trunk at this point. > > starting svn operation > svn update --revision HEAD > in dir /home/twistbot/pybot/trunk.gheorghiu-x86/build (timeout 1200 secs) > svn: PROPFIND request failed on '/pr

Re: [Python-Dev] Promoting PCbuild8 (Was: Python 2.5 performance)

2006-10-17 Thread Grig Gheorghiu
On 10/17/06, Kristján V. Jónsson <[EMAIL PROTECTED]> wrote: > > Okay, a buildbot then doesn't sound quite that scary. Any info somewhere on > how to set one up on a windows box? > http://wiki.python.org/moin/BuildbotOnWindows Grig ___ Python-Dev mail

[Python-Dev] BRANCH FREEZE release24-maint, Wed 18th Oct, 00:00UTC

2006-10-17 Thread Anthony Baxter
I'm declaring the branch frozen for 2.4.4 final from 00:00 UTC (that's about 8 hours from now). The release will either be Wednesday 18th or Thursday 19th. There's a blocking bug http://www.python.org/sf/1578513 - I've attached a patch for it, if someone with autoconf knowledge wants to review t

Re: [Python-Dev] Promoting PCbuild8 (Was: Python 2.5 performance)

2006-10-17 Thread Kristján V . Jónsson
Okay, a buildbot then doesn't sound quite that scary. Any info somewhere on how to set one up on a windows box? I Also wasn't suggesting that we change the PCBuild directory, since I think we definitely want to keep the old support. But I agree that getting regular builds running would be a

[Python-Dev] svn.python.org down

2006-10-17 Thread Grig Gheorghiu
FYI -- can't do svn checkouts/updates from the trunk at this point. starting svn operation svn update --revision HEAD in dir /home/twistbot/pybot/trunk.gheorghiu-x86/build (timeout 1200 secs) svn: PROPFIND request failed on '/projects/python/trunk' svn: PROPFIND of '/projects/python/trunk': could

Re: [Python-Dev] 2.3.6 for the unicode buffer overrun

2006-10-17 Thread Anthony Baxter
On Tuesday 17 October 2006 19:09, Fredrik Lundh wrote: > > But I'm certainly thinking if there's a 2.3.6, it's going to be 2.3.5 > > with the email fix and the unicode repr() fix, and that's it. > > sounds good to me. how much work would that be, and if you're willing to > coordinate, is there any

Re: [Python-Dev] 2.3.6 for the unicode buffer overrun

2006-10-17 Thread Fredrik Lundh
Anthony Baxter wrote: > > why not just do a "2.3.5+security" source release, and leave the rest to > > the downstream maintainers? > > I think we'd need to renumber it to 2.3.6 at least, otherwise there's the > problem of distinguishing between the two. I'd _hope_ that all the > downstreams will h

Re: [Python-Dev] 2.3.6 for the unicode buffer overrun

2006-10-17 Thread Fredrik Lundh
Steve Holden wrote: > Or you can start to promote Django again ... my original plan would still work, I think: http://effbot.org/zone/pydotorg-cache.htm#todo ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/lis

Re: [Python-Dev] 2.3.6 for the unicode buffer overrun

2006-10-17 Thread Anthony Baxter
On Tuesday 17 October 2006 18:54, Fredrik Lundh wrote: > Martin v. L�wis wrote: > > In 2.3.6, there wouldn't just be that change, but also a few other > > changes that have been collected, some relevant for Windows as well > > why not just do a "2.3.5+security" source release, and leave the rest to

Re: [Python-Dev] 2.3.6 for the unicode buffer overrun

2006-10-17 Thread Fredrik Lundh
Martin v. Löwis wrote: > In 2.3.6, there wouldn't just be that change, but also a few other > changes that have been collected, some relevant for Windows as well why not just do a "2.3.5+security" source release, and leave the rest to the downstream maintainers?