On 6/19/06, Trent Mick <[EMAIL PROTECTED]> wrote:
> Trent Mick wrote:
> > Trent Mick wrote:
> >> * [ 1462338 ] upgrade pyexpat to expat 2.0.0
> >>http://python.org/sf/1462338
> >>
> >> * [ 1295808 ] expat symbols should be namespaced in pyexpat
> >>http://python.org/sf/1295808
> >
> > These
Trent Mick wrote:
> Trent Mick wrote:
>> * [ 1462338 ] upgrade pyexpat to expat 2.0.0
>>http://python.org/sf/1462338
>>
>> * [ 1295808 ] expat symbols should be namespaced in pyexpat
>>http://python.org/sf/1295808
>
> These are in now. I don't see any failures yet, either on the buildbots
Trent Mick wrote:
> * [ 1462338 ] upgrade pyexpat to expat 2.0.0
>http://python.org/sf/1462338
>
> * [ 1295808 ] expat symbols should be namespaced in pyexpat
>http://python.org/sf/1295808
These are in now. I don't see any failures yet, either on the buildbots
or on the Windows/Linux/Mac
[Neal Norwitz wrote on June 8th]
> It's June 9 in most parts of the world. The schedule calls for beta 1
> on June 14. That means there's less than 4 days until the expected
> code freeze. Please don't rush to get everything in at the last
> minute. The buildbots should remain green to keep Ant
On Saturday 01 January 2000 09:11, Thomas Heller wrote:
> Neal Norwitz wrote:
> > It's June 9 in most parts of the world. The schedule calls for
> > beta 1 on June 14.
>
> It*s June 14 no longer in too many parts of the world ;-).
> Any *official* news about beta1? I guess the release will not be
arts of the world. From your message:
> From: Thomas Heller <[EMAIL PROTECTED]>
> To: python-dev@python.org
> Date: Fri, 31 Dec 1999 23:11:35 +0100
> Subject: Re: [Python-Dev] beta1 coming real soon
Stolen Guido's time machine, have we?
Charles
--
---
Neal Norwitz wrote:
> It's June 9 in most parts of the world. The schedule calls for beta 1
> on June 14.
It*s June 14 no longer in too many parts of the world ;-).
Any *official* news about beta1? I guess the release will not be started
as long as the tests fail, but is there a new plan?
Thoma
Walter Dörwald wrote:
> And passing MB_ERR_INVALID_CHARS in a call to MultiByteToWideChar()
> doesn't help either, because AFAICT there's no information about the
> error location. What could work would be to try MultiByteToWideChar()
> with various string lengths to try to determine whether the er
Martin v. Löwis wrote:
> Walter Dörwald wrote:
The best way to throughly test the patch is of course to check it in. ;)
>>> Is it too risky? ;)
>> At least I'd like to get a second review of the patch.
>
> I've reviewed it, and am likely to check it in.
Great!
> I notice that the
> patch s
Walter Dörwald wrote:
>>> The best way to throughly test the patch is of course to check it in. ;)
>> Is it too risky? ;)
>
> At least I'd like to get a second review of the patch.
I've reviewed it, and am likely to check it in. I notice that the
patch still has problems. In particular, it is lim
H.Yamamoto wrote:
> - Original Message -
> From: "Walter Dörwald" <[EMAIL PROTECTED]>
> To: "H.Yamamoto" <[EMAIL PROTECTED]>
> Cc: "python-dev"
> Sent: Friday, June 09, 2006 7:56 PM
> Subject: Re: [Python-Dev] beta1 coming re
Barry Warsaw wrote:
> On Fri, 9 Jun 2006 09:54:29 -0700
> "Brett Cannon" <[EMAIL PROTECTED]> wrote:
>
>> Do enough people use Google Calendar or a calendar app that support
>> iCal feeds that it would be useful for someone to maintain a Gcal
>> calendar that has the various Python dev related date
On 10-jun-2006, at 21:32, Aahz wrote:
> On Sat, Jun 10, 2006, Ronald Oussoren wrote:
>>
>> Hopefully Python 2.5 will see more testing on the mac because there
>> will be prompt binary releases of the betas this time around.
>
> If there is in fact a binary beta release for OS X, there will
> defi
On Sat, Jun 10, 2006, Ronald Oussoren wrote:
>
> Hopefully Python 2.5 will see more testing on the mac because there
> will be prompt binary releases of the betas this time around.
If there is in fact a binary beta release for OS X, there will
definitely be testing because we need to double-chec
On 9-jun-2006, at 20:22, Martin v. Löwis wrote:
> Ronald Oussoren wrote:
>> How hard is the feature freeze? Would it be possible to update the
>> Carbon bindings after beta1? Given Apple's focus on backward
>> compatibility the update should only add new functionality, not
>> remove existing func
On 6/10/06, Ka-Ping Yee <[EMAIL PROTECTED]> wrote:
> On Sat, 10 Jun 2006, Paul Moore wrote:
> > Actually, the code uses "ifconfig", which doesn't exist on Windows.
> > You want the command "ipconfig /all".
>
> I fixed that before you posted this message. :)
Give Guido the time machine keys back! :
On Sat, 10 Jun 2006, Paul Moore wrote:
> Actually, the code uses "ifconfig", which doesn't exist on Windows.
> You want the command "ipconfig /all".
I fixed that before you posted this message. :)
-- ?!ng
___
Python-Dev mailing list
Python-Dev@python.o
On 6/10/06, Johan Dahlin <[EMAIL PROTECTED]> wrote:
> Ka-Ping Yee wrote:
> > On Thu, 8 Jun 2006, Neal Norwitz wrote:
> >> If you plan to make a checkin adding a feature (even a simple one),
> >> you oughta let people know by responding to this message. Please get
> >> the bug fixes in ASAP. Remem
Ka-Ping Yee wrote:
> On Thu, 8 Jun 2006, Neal Norwitz wrote:
>> If you plan to make a checkin adding a feature (even a simple one),
>> you oughta let people know by responding to this message. Please get
>> the bug fixes in ASAP. Remember to add tests!
>
> Just to make this appear on this thread
On Thu, 8 Jun 2006, Neal Norwitz wrote:
> If you plan to make a checkin adding a feature (even a simple one),
> you oughta let people know by responding to this message. Please get
> the bug fixes in ASAP. Remember to add tests!
Just to make this appear on this thread: i'm planning to check in
t
Neal Norwitz wrote:
> It's June 9 in most parts of the world. The schedule calls for beta 1
> on June 14. That means there's less than 4 days until the expected
> code freeze. Please don't rush to get everything in at the last
> minute. The buildbots should remain green to keep Anthony happy an
- Original Message -
From: "Walter Dörwald" <[EMAIL PROTECTED]>
To: "H.Yamamoto" <[EMAIL PROTECTED]>
Cc: "python-dev"
Sent: Friday, June 09, 2006 7:56 PM
Subject: Re: [Python-Dev] beta1 coming real soon
> The best way to throughly test the
Ronald Oussoren wrote:
> How hard is the feature freeze? Would it be possible to update the
> Carbon bindings after beta1? Given Apple's focus on backward
> compatibility the update should only add new functionality, not
> remove existing functions/types.
I'd say it's absolute wrt. to requir
Thomas Heller wrote:
>> If you plan to make a checkin adding a feature (even a simple one),
>> you oughta let people know by responding to this message. Please get
>> the bug fixes in ASAP. Remember to add tests!
>
> The other question is about feature freeze on external libraries.
> Is it stric
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 9 Jun 2006 09:54:29 -0700
"Brett Cannon" <[EMAIL PROTECTED]> wrote:
> Do enough people use Google Calendar or a calendar app that support
> iCal feeds that it would be useful for someone to maintain a Gcal
> calendar that has the various Pytho
On 6/9/06, Thomas Heller <[EMAIL PROTECTED]> wrote:
Neal Norwitz wrote:> It's June 9 in most parts of the world. The schedule calls for beta 1> on June 14. That means there's less than 4 days until the expected> code freeze. Please don't rush to get everything in at the last
> minute. The build
On 9-jun-2006, at 17:34, Thomas Heller wrote:
>
>
> The other question is about feature freeze on external libraries.
> Is it strictly forbidden to add new features in ctypes during the
> (Python) beta period?
Now that you mention the feature freeze...
The tools that generate the Carbon binding
On 9-jun-2006, at 8:23, Neal Norwitz wrote:
> It's June 9 in most parts of the world. The schedule calls for beta 1
> on June 14. That means there's less than 4 days until the expected
> code freeze. Please don't rush to get everything in at the last
> minute. The buildbots should remain gree
Neal Norwitz wrote:
> It's June 9 in most parts of the world. The schedule calls for beta 1
> on June 14. That means there's less than 4 days until the expected
> code freeze. Please don't rush to get everything in at the last
> minute. The buildbots should remain green to keep Anthony happy an
Neal Norwitz wrote:
> It's June 9 in most parts of the world. The schedule calls for beta 1
> on June 14. That means there's less than 4 days until the expected
> code freeze. Please don't rush to get everything in at the last
> minute. The buildbots should remain green to keep Anthony happy an
"Neal Norwitz" <[EMAIL PROTECTED]> writes:
> It's June 9 in most parts of the world. The schedule calls for beta 1
> on June 14. That means there's less than 4 days until the expected
> code freeze. Please don't rush to get everything in at the last
> minute. The buildbots should remain green
would be added conditionally to errors.c and pyerrors.h, and macros
defined in pyerrors.h.
Any objections?
Kristján
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neal Norwitz
Sent: 9. júní 2006 06:24
To: Python Dev
Subject: [Python-Dev] beta1 coming
H.Yamamoto wrote:
>> If you plan to make a checkin adding a feature (even a simple one),
>> you oughta let people know by responding to this message. Please get
>> the bug fixes in ASAP. Remember to add tests!
>
> Is there any chance to fix mbcs bug? I think this is critical...
> My patch is he
> If you plan to make a checkin adding a feature (even a simple one),
> you oughta let people know by responding to this message. Please get
> the bug fixes in ASAP. Remember to add tests!
Is there any chance to fix mbcs bug? I think this is critical...
My patch is here: http://python.org/sf/145
Neal Norwitz wrote:
> It's June 9 in most parts of the world. The schedule calls for beta 1
> on June 14. That means there's less than 4 days until the expected
> code freeze. Please don't rush to get everything in at the last
> minute. The buildbots should remain green to keep Anthony happy an
Neal Norwitz wrote:
> It's June 9 in most parts of the world. The schedule calls for beta 1
> on June 14. That means there's less than 4 days until the expected
> code freeze. Please don't rush to get everything in at the last
> minute. The buildbots should remain green to keep Anthony happy an
It's June 9 in most parts of the world. The schedule calls for beta 1
on June 14. That means there's less than 4 days until the expected
code freeze. Please don't rush to get everything in at the last
minute. The buildbots should remain green to keep Anthony happy and
me sane (or is it the othe
37 matches
Mail list logo
