I suggest that there be a third beta release and that we then wait just
a bit before going final.
The bugs that were found and fixed in the first two beta releases
suggest that Py2.5 is not yet as stable as we would like. Over the next
few days, I'll try to run it on as much third-party code a
On Friday 28 July 2006 15:32, Raymond Hettinger wrote:
> I suggest that there be a third beta release and that we then wait
> just a bit before going final.
>
> The bugs that were found and fixed in the first two beta releases
> suggest that Py2.5 is not yet as stable as we would like. Over the
>
Anthony Baxter <[EMAIL PROTECTED]> writes:
> On Friday 28 July 2006 15:32, Raymond Hettinger wrote:
>> I suggest that there be a third beta release and that we then wait
>> just a bit before going final.
>>
>> The bugs that were found and fixed in the first two beta releases
>> suggest that Py2.5
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 28, 2006, at 1:39 AM, Anthony Baxter wrote:
> I've been thinking the same thing, too. A quick chat to Neal says that
> he also agrees.
>
> There's still a lot more bugs popping up than I'm really comfortable
> with. I guess this is inevitable -
On 7/28/06, Michael Hudson <[EMAIL PROTECTED]> wrote:
> Anthony Baxter <[EMAIL PROTECTED]> writes:
>
> > Does anyone disagree with making the next release beta3?
>
> It seems like a good idea to me. I guess this will mean the final
> release will be pushed back a bit?
Anthony and I talked about s
Neal Norwitz wrote:
>Anthony and I talked about still having b3 on Aug 1. rc1 around Aug
>17-18 (just before the Google sprint which Martin, Jeremy and I will
>be attending). Final around 24-29. We didn't discuss with Martin
>yet, so these dates are quite tentative.
>
>
If it doesn't muck-up
Neal Norwitz wrote:
> Anthony and I talked about still having b3 on Aug 1. rc1 around Aug
> 17-18 (just before the Google sprint which Martin, Jeremy and I will
> be attending). Final around 24-29. We didn't discuss with Martin
> yet, so these dates are quite tentative.
That doesn't work for me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Re: Python 2.5 compatibility
On Jul 28, 2006, at 8:57 AM, Barry Warsaw wrote:
> +1. It would give me more type to port and test a few of my
> applications to the new version.
>
> I'm still working on Mailman but the most painful thing so far has
On Sunday 30 July 2006 15:44, Barry Warsaw wrote:
> if isinstance(obj, ClassType) or isinstance(obj, type(type))
Looks like you've got a possible name clash in the second isinstance. ;-)
-Fred
--
Fred L. Drake, Jr.
___
Python-Dev mailing list
Barry Warsaw wrote:
> if isinstance(obj, ClassType)
>
> which fails in Python 2.5. I actually rewrote it like so:
>
> if isinstance(obj, ClassType) or isinstance(obj, type(type))
The second "type" seems to be superfluous. ;)
Georg
___
Python-Dev ma
On Sunday 30 July 2006 16:17, Georg Brandl wrote:
> The second "type" seems to be superfluous. ;)
I was thinking it suggested there was a local named "type". But if not, yeah.
I get the impression Barry's pretty new to this "Python thing." Wonder what
he's been up to. ;-)
-Fred
--
Fred
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 30, 2006, at 4:27 PM, Fred L. Drake, Jr. wrote:
> On Sunday 30 July 2006 16:17, Georg Brandl wrote:
>> The second "type" seems to be superfluous. ;)
>
> I was thinking it suggested there was a local named "type". But if
> not, yeah.
>
> I ge
Fred L. Drake, Jr. schrieb:
> On Sunday 30 July 2006 15:44, Barry Warsaw wrote:
> > if isinstance(obj, ClassType) or isinstance(obj, type(type))
>
> Looks like you've got a possible name clash in the second isinstance. ;-)
Nah, that's rather an entry to the obfuscated Python contest.
The two oc
13 matches
Mail list logo