Re: [Python-Dev] Buildbots for trunk are all red
On Feb 27, 2008, at 10:45 PM, Fred Drake wrote: > On Feb 27, 2008, at 9:13 AM, A.M. Kuchling wrote: >> Doing a code search finds a fair number of users of the module: >> Zope's >> BDBStorage, ... > > The BDBStorage is long gone at this point. Few are so unfortunate as > to remember it (though a few who may just might be on this list). :-) Age related memory loss has its upside, I guess. -B ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Code freeze?
Hey Barry! When are you planing to freeze the code of the trunk and branches/py3k for the upcoming alpha releases? I'll merge the last modifications from 2.6 to 3.0 in a couple of minutes. All tests on Linux are looking good, except for the two profile tests on 3.0. I'm going to test Windows later. Christian ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Buildbots for trunk are all red
Fred Drake wrote: > The BDBStorage is long gone at this point. Few are so unfortunate as > to remember it (though a few who may just might be on this list). :-) Oh yeah ... ZODB4 and BDBStorage ... a dark chapter starting with high hopes and ending in tragedy ... Several projects like Zope and Subversion worked hard on a a Berkeley DB backend but in the end all projects had the same fate. A few years ago in Göteborg/SE during lunch Jim explained me the reasons for the cancellation. As far as I remember the conversation he used some words I dare not to repeat in public. Some kids may read the Python dev list. :) Christian ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-3000] Code freeze?
On Thu, Feb 28, 2008 at 1:49 PM, Christian Heimes <[EMAIL PROTECTED]> wrote: > Hey Barry! > > When are you planing to freeze the code of the trunk and branches/py3k > for the upcoming alpha releases? I'll merge the last modifications from > 2.6 to 3.0 in a couple of minutes. All tests on Linux are looking good, > except for the two profile tests on 3.0. I'm going to test Windows later. > Would a call for third-party module maintainer updates be justified? pysqlite in particular has advanced a couple versions since 2.5, and it'd be nice if the latest made it into 2.6. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Google Summer of Code 2008
The Google Summer of Code is on again and I've been asked to coordinate the PSF's involvement. You can find out more about GSoC at http://code.google.com/soc/2008/ There is also a page on the Python wiki: http://wiki.python.org/moin/SummerOfCode Although the PSF does act as an umbrella organization for a number of different projects, we'd like to give as much opportunity as possible for students to work on core Python development. At this stage it would be great if you could start thinking about potential projects and/or whether you would be willing to be a mentor. Two mailing lists have been set up: http://mail.python.org/mailman/listinfo/soc2008-mentors http://mail.python.org/mailman/listinfo/soc2008-general If you are interested in being a mentor, please join both lists. The mentor list requires approval and the archive is private. The general list is for anyone interested in the summer of code and all potential mentors, potential students and interested lurkers should join. Let me know if you have any questions. James -- James Tauber http://jtauber.com/ journeyman of somehttp://jtauber.com/blog/ ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Buildbots for trunk are all red
On Thu, Feb 28, 2008 at 09:00:54PM +0100, Christian Heimes wrote: > Oh yeah ... ZODB4 and BDBStorage ... a dark chapter starting with high > hopes and ending in tragedy ... Several projects like Zope and > Subversion worked hard on a a Berkeley DB backend but in the end all > projects had the same fate. > > A few years ago in Geteborg/SE during lunch Jim explained me the reasons > for the cancellation. As far as I remember the conversation he used some > words I dare not to repeat in public. Some kids may read the Python dev > list. :) Sorry, can I ask an additional question? These words - what they were about? about the architecture of BDBStorage and Subversion, or about the very BerkeleyDB, or about what? Oleg. -- Oleg Broytmannhttp://phd.pp.ru/[EMAIL PROTECTED] Programmers don't die, they just GOSUB without RETURN. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Buildbots for trunk are all red
Guido van Rossum wrote: > Correction: the subversion BerkeleyDB backend is still very much alive > and kicking. There were some early issues (they did things that > SleepyCat told them not to do :-) but it was corrected and it's still > working fine for several large users. Thanks for the correction! It seems my information is a bit outdated. Several years ago we have moved most or all subversion repositories to fsfs because we had major issue with the Berkeley backend. I haven't used the bdb backend since then. Christian ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Buildbots for trunk are all red
On Thu, Feb 28, 2008 at 12:23 PM, Christian Heimes <[EMAIL PROTECTED]> wrote: > Guido van Rossum wrote: > > Correction: the subversion BerkeleyDB backend is still very much alive > > and kicking. There were some early issues (they did things that > > SleepyCat told them not to do :-) but it was corrected and it's still > > working fine for several large users. > > Thanks for the correction! It seems my information is a bit outdated. > Several years ago we have moved most or all subversion repositories to > fsfs because we had major issue with the Berkeley backend. I haven't > used the bdb backend since then. This was the fault of the svn developers, not of BerkeleyDB. And svn has fixed the issues. -- --Guido van Rossum (home page: http://www.python.org/~guido/) ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Buildbots for trunk are all red
Guido van Rossum wrote: > This was the fault of the svn developers, not of BerkeleyDB. And svn > has fixed the issues. I got that in your last mail ;) Christian ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Buildbots for trunk are all red
Correction: the subversion BerkeleyDB backend is still very much alive and kicking. There were some early issues (they did things that SleepyCat told them not to do :-) but it was corrected and it's still working fine for several large users. On Thu, Feb 28, 2008 at 12:00 PM, Christian Heimes <[EMAIL PROTECTED]> wrote: > Fred Drake wrote: > > The BDBStorage is long gone at this point. Few are so unfortunate as > > to remember it (though a few who may just might be on this list). :-) > > Oh yeah ... ZODB4 and BDBStorage ... a dark chapter starting with high > hopes and ending in tragedy ... Several projects like Zope and > Subversion worked hard on a a Berkeley DB backend but in the end all > projects had the same fate. > > A few years ago in Göteborg/SE during lunch Jim explained me the reasons > for the cancellation. As far as I remember the conversation he used some > words I dare not to repeat in public. Some kids may read the Python dev > list. :) > > Christian > > > ___ > Python-Dev mailing list > [email protected] > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/guido%40python.org > -- --Guido van Rossum (home page: http://www.python.org/~guido/) ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Buildbots for trunk are all red
Oleg Broytmann wrote: >Sorry, can I ask an additional question? These words - what they were > about? about the architecture of BDBStorage and Subversion, or about the > very BerkeleyDB, or about what? I don't know all details and it was several years ago so some of my saying may not be correct. I wasn't involved in the project. Please contact Jim Fulton from Zope Corp if you are interested in more details. More than 5 years ago Zope Corp was working on a Berkeley DB backend for ZODB. It was more of a marketing decision to show large companies that ZODB is using a well known database instead of a self made one. The project failed due to problems with the Berkeley db. I vaguely remember something with transactions and speed ... Christian ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Code freeze?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 28, 2008, at 2:49 PM, Christian Heimes wrote: > Hey Barry! Hi Christian! > When are you planing to freeze the code of the trunk and branches/py3k > for the upcoming alpha releases? I'll merge the last modifications > from > 2.6 to 3.0 in a couple of minutes. All tests on Linux are looking > good, > except for the two profile tests on 3.0. I'm going to test Windows > later. Okay, let's go ahead and make it official. I plan on cutting the alphas for 2.6 and 3.0 at about 6pm Eastern (UTC-5) time or 2300 UTC. Let's freeze the tree one hour prior to that: 2200 UTC Friday 29-Feb-2008. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iQCVAwUBR8cewnEjvBPtnXfVAQJSpQP/aWjpFbTAETdHGnp0IOEagaXNojwJEBBl llFAE6FQI+WjPxNDAG6Y8T0y4kdiBVubMA7yfp+wXZdn+zpO/4D5OtBVeAoGVjLj Tg1Ws1Y2uEf7Ah4lRqLya1tfgO+rnKJ38vsCit58XACYVGKWDpD0mVu+An7+6Jmj rtlEjwGpvFQ= =jIiD -END PGP SIGNATURE- ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-3000] Code freeze?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 28, 2008, at 3:03 PM, Chris Mellon wrote: > On Thu, Feb 28, 2008 at 1:49 PM, Christian Heimes <[EMAIL PROTECTED]> > wrote: >> Hey Barry! >> >> When are you planing to freeze the code of the trunk and branches/ >> py3k >> for the upcoming alpha releases? I'll merge the last modifications >> from >> 2.6 to 3.0 in a couple of minutes. All tests on Linux are looking >> good, >> except for the two profile tests on 3.0. I'm going to test Windows >> later. >> > > Would a call for third-party module maintainer updates be justified? > pysqlite in particular has advanced a couple versions since 2.5, and > it'd be nice if the latest made it into 2.6. There's still plenty of time for stuff to make it into 2.6 -- this is only an alpha release! I encourage people to get their changes in now if they want them reflected in the next alphas, but I intend to cut the release from whatever's in svn at 2300 UTC tomorrow. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iQCVAwUBR8cfvnEjvBPtnXfVAQJKSwP+M5RzAFsQ3fNSwwYzRa+j3EaocwLgWJ+i QVLxALoH+ha6yWQDmdQJCvm4H+DPBSnz9o/ejuJ3Wuhf9TEIWBLjuwB1rM8qm7mB blaaNVV9eOXfORjlQ3PvwGblfwmGMGFUKfTuta8BZqkxtEzNKL5tDvgVdx98rbTV VEyfj7ap3BM= =dsql -END PGP SIGNATURE- ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Code freeze?
Barry Warsaw wrote: > Okay, let's go ahead and make it official. > > I plan on cutting the alphas for 2.6 and 3.0 at about 6pm Eastern > (UTC-5) time or 2300 UTC. Let's freeze the tree one hour prior to > that: 2200 UTC Friday 29-Feb-2008. Linux is looking good. I've fixed some minor Windows issue in the last 30 minutes. I found one strange behavior. Some tests were failing because iter(fileobj) where fileobj is a tempfile._TemporaryFileWrapper failed. Apparently iter() doesn't use __getattr__ to acquire the __iter__ method. Is this behavior deliberately? Christian signature.asc Description: OpenPGP digital signature ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-3000] Code freeze?
Barry Warsaw wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Feb 28, 2008, at 2:49 PM, Christian Heimes wrote: > >> Hey Barry! > > Hi Christian! > >> When are you planing to freeze the code of the trunk and branches/py3k >> for the upcoming alpha releases? I'll merge the last modifications >> from >> 2.6 to 3.0 in a couple of minutes. All tests on Linux are looking >> good, >> except for the two profile tests on 3.0. I'm going to test Windows >> later. > > Okay, let's go ahead and make it official. > > I plan on cutting the alphas for 2.6 and 3.0 at about 6pm Eastern > (UTC-5) time or 2300 UTC. Let's freeze the tree one hour prior to > that: 2200 UTC Friday 29-Feb-2008. Argh! I was going to check the last of the PEP 3127 changes in tonight, but I won't make it by 6 pm EST. I have them finished, but no tests written, so I'm not comfortable checking them in yet. I guess it's no big deal that they slip until the next alpha. Eric. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Code freeze?
Barry Warsaw writes: > I plan on cutting the alphas for 2.6 and 3.0 at about 6pm Eastern > (UTC-5) time or 2300 UTC. Let's freeze the tree one hour prior to > that: 2200 UTC Friday 29-Feb-2008. Is that enough time for the buildbots to do their thing and for you to look at the page? Alterntaively, I guess you could just suggest that people check the buildbot page for their platforms before downloading ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-3000] Code freeze?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 28, 2008, at 4:03 PM, Eric Smith wrote: > Barry Warsaw wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> On Feb 28, 2008, at 2:49 PM, Christian Heimes wrote: >>> Hey Barry! >> Hi Christian! >>> When are you planing to freeze the code of the trunk and branches/ >>> py3k >>> for the upcoming alpha releases? I'll merge the last >>> modifications from >>> 2.6 to 3.0 in a couple of minutes. All tests on Linux are looking >>> good, >>> except for the two profile tests on 3.0. I'm going to test >>> Windows later. >> Okay, let's go ahead and make it official. >> I plan on cutting the alphas for 2.6 and 3.0 at about 6pm Eastern >> (UTC-5) time or 2300 UTC. Let's freeze the tree one hour prior to >> that: 2200 UTC Friday 29-Feb-2008. > > Argh! I was going to check the last of the PEP 3127 changes in > tonight, but I won't make it by 6 pm EST. I have them finished, but > no tests written, so I'm not comfortable checking them in yet. I > guess it's no big deal that they slip until the next alpha. Sorry, I notice my message might not have been clear. As of this writing, you have 23 hours and 54 minute before code freeze :). Code freeze: 2200 UTC 29-Feb-2008 Alpha making: 2300 UTC 29-Feb-2008 - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iQCVAwUBR8cwh3EjvBPtnXfVAQLRSAP/XalWCb1ArFUxoa0OQlA0T7Rw7Si3AFYu mXRTlU0kqptiYDiHYbPaQwzFwI3xgUBCG5qUnFFq3PCLrxmd6ilYcWAhErSGmxOS PAWfmrxZElAxqXHviOPQw5dlnoD8JhDudArgn74zRHHluazZYR4r+fCvN8fV0gKc zRDt8Owdwng= =uCn6 -END PGP SIGNATURE- ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Code freeze?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 28, 2008, at 5:07 PM, Stephen J. Turnbull wrote: > Barry Warsaw writes: > >> I plan on cutting the alphas for 2.6 and 3.0 at about 6pm Eastern >> (UTC-5) time or 2300 UTC. Let's freeze the tree one hour prior to >> that: 2200 UTC Friday 29-Feb-2008. > > Is that enough time for the buildbots to do their thing and for you to > look at the page? I don't know, but we'll find out! The first time (in years) will be a bit of a trial-and-error for me. I can always get dinner in the middle of it. :) > Alterntaively, I guess you could just suggest that people check the > buildbot page for their platforms before downloading Yes, good idea. I'm only going to cut source tarballs for the alphas. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iQCVAwUBR8cxKXEjvBPtnXfVAQLgqwQAiiQUL1lhQM6EmYr8bvZNW2h97ziKGtpf mVTiNOCJZ1xZ6vKkcmR3Asd+Cwm7B2eT+sVLEpq+Z6tbki+7o0wXC4V6h/ar+zMz dQcR0QdwM218hioOiIVhtZXbWUTLGndWVviKBcoOdw6qwTbWFspCMV0+FEzdiNUN V0bDUjn4zkI= =uPib -END PGP SIGNATURE- ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-3000] Code freeze?
Barry Warsaw wrote: >>> Okay, let's go ahead and make it official. >>> I plan on cutting the alphas for 2.6 and 3.0 at about 6pm Eastern >>> (UTC-5) time or 2300 UTC. Let's freeze the tree one hour prior to >>> that: 2200 UTC Friday 29-Feb-2008. >> >> Argh! I was going to check the last of the PEP 3127 changes in >> tonight, but I won't make it by 6 pm EST. I have them finished, but >> no tests written, so I'm not comfortable checking them in yet. I >> guess it's no big deal that they slip until the next alpha. > > Sorry, I notice my message might not have been clear. As of this > writing, you have 23 hours and 54 minute before code freeze :). > > Code freeze: 2200 UTC 29-Feb-2008 > Alpha making: 2300 UTC 29-Feb-2008 Your message was clear, it's my reading comprehension that is low. Now you've removed my excuse for not getting this done. To the keyboard! Eric. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Google Summer of Code 2008
2008/2/28, James Tauber <[EMAIL PROTECTED]>: > The Google Summer of Code is on again and I've been asked to coordinate > the PSF's involvement. These are great news, specially the second one, :) Regards, -- .Facundo Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org/ar/ ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Fixing buildbot/external(-amd64).bat files on Windows
Howdy, I'm going through the motions of getting my newly added build slave in a half decent state. The external.bat and external-amd64.bat files needed the following in order to build db-4.4.20: Index: external.bat === --- external.bat(revision 61125) +++ external.bat(working copy) @@ -10,7 +10,8 @@ @rem Sleepycat db if not exist db-4.4.20 svn export http://svn.python.org/projects/external/db-4.4.20 if not exist db-4.4.20\build_win32\debug\libdb44sd.lib ( - vcbuild db-4.4.20\build_win32\Berkeley_DB.sln /build Debug /project db_static + devenv /upgrade db-4.4.20\build_win32\Berkeley_DB.sln + devenv db-4.4.20\build_win32\Berkeley_DB.sln /build Debug /project db_static ) @rem OpenSSL (This is against trunk, same thing would apply to py3k I guess, given that we're using %VS90COMNTOOLS%vsvars32.bat there too.) Regards, Trent. -- http://www.onresolve.com external.bat.patch Description: external.bat.patch external-amd64.bat.patch Description: external-amd64.bat.patch ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
