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
===
--- externa
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/
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 th
-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
-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 cod
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?
Alter
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 mo
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 iss
-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 alp
-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
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 correc
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 <[EM
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
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/p
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
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 correcti
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
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 organizat
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 a
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
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
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
21 matches
Mail list logo
