On 22-Jan-08, at 8:47 PM, Guido van Rossum wrote:
> While the exact release schedule for 2.5.2 is still up in the air, I
> expect that it will be within a few weeks. This means that we need to
> make sure that anything that should go into 2.5.2 goes in ASAP,
> preferably this week. It also means t
> But on windows, ":" is special letter after drive letter. (ex:
> "C:/Winnt/foo/bar")
> So I imagine open() or something converts ":" to "!" (valid character as
> file name).
Sorry, I lied. :-(
open() didn't change ":", test_mailbox.py (TestMaildir.setUp) changed
self._box.colon to "!"
Otherwi
> From:
>
http://www.python.org/dev/buildbot/all/x86%20XP-4%202.5/builds/107/step-test/0
>
> The errors are:
>
> File
"E:\cygwin\home\db3l\buildarea\2.5.bolen-windows\build\lib\test\test_mailbox
.py",
> line 522, in test_consistent_factory
> msg2 = box.get_message(key)
> File
"E:\cygwin\hom
Neal Norwitz schrieb:
> We need to fix the Windows buildbots. 2 tests are currently failing
> for 2.5.2: test_mailbox test_winreg
The test_winreg failure is a funny one:
The py3k test_winreg fails because of a bug in the test itself; I fixed
this in rev. 60236. The failing test leaves a key in
We need to fix the Windows buildbots. 2 tests are currently failing
for 2.5.2: test_mailbox test_winreg
From:
http://www.python.org/dev/buildbot/all/x86%20XP-4%202.5/builds/107/step-test/0
The errors are:
File
"E:\cygwin\home\db3l\buildarea\2.5.bolen-windows\build\lib\test\test_mailbox.py
>> Is threre any chance to fix this bug before releasing 2.5.2?
>> http://bugs.python.org/issue1736
>> It contains potential buffer overrun, I think this is somewhat important.
>> If multibyte support (CharNext) is not needed, I 'll rewrite the patch
>> gracefully.
>
> I'll leave that to MvL to d
On Jan 23, 2008 7:28 PM, ocean <[EMAIL PROTECTED]> wrote:
> Is threre any chance to fix this bug before releasing 2.5.2?
> http://bugs.python.org/issue1736
> It contains potential buffer overrun, I think this is somewhat important.
> If multibyte support (CharNext) is not needed, I 'll rewrite the
Is threre any chance to fix this bug before releasing 2.5.2?
http://bugs.python.org/issue1736
It contains potential buffer overrun, I think this is somewhat important.
If multibyte support (CharNext) is not needed, I 'll rewrite the patch
gracefully.
__
Guido van Rossum wrote:
> On Jan 23, 2008 12:25 PM, Steve Holden <[EMAIL PROTECTED]> wrote:
>> Giampaolo Rodola' wrote:
Also, *nothing* should go into the 2.4 branch any more *except*
important security patches.
>> ^
>>> http://bugs.python.org/issue1745035
>>> I guess this one
On Jan 23, 2008 12:25 PM, Steve Holden <[EMAIL PROTECTED]> wrote:
> Giampaolo Rodola' wrote:
> >> Also, *nothing* should go into the 2.4 branch any more *except*
> >> important security patches.
> ^
> >
> > http://bugs.python.org/issue1745035
> > I guess this one should concern both 2.4
Giampaolo Rodola' wrote:
>> Also, *nothing* should go into the 2.4 branch any more *except*
>> important security patches.
^
>
> http://bugs.python.org/issue1745035
> I guess this one should concern both 2.4 and 2.5 branches.
>
Egregious though the error may be I can't myself see tha
> Also, *nothing* should go into the 2.4 branch any more *except*
> important security patches.
http://bugs.python.org/issue1745035
I guess this one should concern both 2.4 and 2.5 branches.
On 23 Gen, 05:47, "Guido van Rossum" <[EMAIL PROTECTED]> wrote:
> While the exact release schedule for 2.5
Brett Cannon writes:
> On Jan 22, 2008 8:47 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > A reminder: 2.5.2 should only get bugfixes, new features.
>
> If Guido felt like dragging the time machine out he would catch his
> mistake and have that say "NO new features".
What, nothing abou
On Jan 22, 2008 8:47 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> While the exact release schedule for 2.5.2 is still up in the air, I
> expect that it will be within a few weeks. This means that we need to
> make sure that anything that should go into 2.5.2 goes in ASAP,
> preferably this wee
While the exact release schedule for 2.5.2 is still up in the air, I
expect that it will be within a few weeks. This means that we need to
make sure that anything that should go into 2.5.2 goes in ASAP,
preferably this week. It also means that we should be very careful
what goes in though -- and we
15 matches
Mail list logo
