-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 9, 2008, at 8:15 AM, [EMAIL PROTECTED] wrote:
In the past I seem to recall that the Python code proper might be
frozen
(for a day or two) before a release, but that it was okay to still
commit
changes to non-code files such as
Christian Heimes wrote:
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
Christian Heimes wrote:
Is this documented somewhere? The docs say See the
:meth:`__getattribute__` method below for a way to actually get total
control over attribute access..
I just checked, and the restriction is now documented in the development
docs in the section on special methods at
Barry Warsaw wrote:
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 29, 2008, at 1:59 PM, Stephen J. Turnbull wrote:
I think that it probably is desirable to to put that deadline pressure
on. Individuals who rush to get their work in, and cause alpha-to-
alpha regressions, can be advised to wait in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 29, 2008, at 1:08 PM, Eric Smith wrote:
Barry Warsaw wrote:
-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,
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
-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?
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
-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
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
11 matches
Mail list logo
