On Thu, Feb 12, 2009 at 1:57 PM, Barry Warsaw wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Feb 12, 2009, at 1:44 PM, Brett Cannon wrote:
>
>> What about the segfault problem? Shouldn't that get in?
>
> If it can be done without a regression, yes. Do it now and that will give
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 12, 2009, at 1:44 PM, Brett Cannon wrote:
What about the segfault problem? Shouldn't that get in?
If it can be done without a regression, yes. Do it now and that will
give the buildbots time to run. If they go red, we'll back it out.
On Thu, Feb 12, 2009 at 10:40, Barry Warsaw wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Feb 12, 2009, at 1:29 PM, Jesse Noller wrote:
>
> On Thu, Feb 12, 2009 at 1:20 PM, Antoine Pitrou
>> wrote:
>>
>>> Jesse Noller gmail.com> writes:
>>>
I'm afraid I've gone bran
On Thu, Feb 12, 2009 at 1:40 PM, Barry Warsaw wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Feb 12, 2009, at 1:29 PM, Jesse Noller wrote:
>
>> On Thu, Feb 12, 2009 at 1:20 PM, Antoine Pitrou
>> wrote:
>>>
>>> Jesse Noller gmail.com> writes:
I'm afraid I've gone branch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 12, 2009, at 1:29 PM, Jesse Noller wrote:
On Thu, Feb 12, 2009 at 1:20 PM, Antoine Pitrou
wrote:
Jesse Noller gmail.com> writes:
I'm afraid I've gone branch-stupid. I have a a few changes that
should
be on the boat for the next relea
On Thu, Feb 12, 2009 at 1:20 PM, Antoine Pitrou wrote:
> Jesse Noller gmail.com> writes:
>>
>> I'm afraid I've gone branch-stupid. I have a a few changes that should
>> be on the boat for the next release, but I can't for the life of me
>> remember which branch to push to - right now the changes
Jesse Noller gmail.com> writes:
>
> I'm afraid I've gone branch-stupid. I have a a few changes that should
> be on the boat for the next release, but I can't for the life of me
> remember which branch to push to - right now the changes are on trunk
> and py3k.
The next release (3.0.1) is tomorro
I'm afraid I've gone branch-stupid. I have a a few changes that should
be on the boat for the next release, but I can't for the life of me
remember which branch to push to - right now the changes are on trunk
and py3k.
-jesse
___
Python-Dev mailing list