It seems logging is broken in 2.6.3. Should we release
2.6.4 quickly?
http://bugs.python.org/issue7052
Regards,
Martin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
Martin v. Löwis schrieb:
> It seems logging is broken in 2.6.3. Should we release
> 2.6.4 quickly?
>
> http://bugs.python.org/issue7052
It also reports a 2.6.3rc1 version number on windows:
Python 2.6.3 (r263rc1:75186, Oct 2 2009, 20:40:30) [MSC v.1500 32 bit (Intel)]
on win32
Type "help", "cop
Le dimanche 04 octobre 2009 à 12:14 +0200, Thomas Heller a écrit :
> Martin v. Löwis schrieb:
> > It seems logging is broken in 2.6.3. Should we release
> > 2.6.4 quickly?
> >
> > http://bugs.python.org/issue7052
Perhaps we should leave a one-week delay between rc and final next time,
so that thi
On Sun, 04 Oct 2009 12:14:23 +0200, "Thomas Heller"
said:
> Martin v. Löwis schrieb:
> > It seems logging is broken in 2.6.3. Should we release
> > 2.6.4 quickly?
> >
> > http://bugs.python.org/issue7052
>
> It also reports a 2.6.3rc1 version number on windows:
>
> Python 2.6.3 (r263rc1:75186,
Antoine> Perhaps we should leave a one-week delay between rc and final
Antoine> next time, so that this kind of late-minute issues have an
Antoine> opportunity to be discovered ?
Yeah, I was a little surprised the final release followed rc1 so quickly.
We were working through some prob
> Found python26.dll in c:\Windows\System32\ with 10/2 date. Clearly this
> was being shadowed by the python26.dll in c:\Python26\. I have no idea
> where that came from - as far as I know, I had a vanilla 2.6.2
> installation, and I don't build Python on Windows.
>
> FWIW to the Windows gurus.
On Sun, 04 Oct 2009 20:20:33 +0200, ""Martin v. Löwis""
said:
> > Found python26.dll in c:\Windows\System32\ with 10/2 date. Clearly this
> > was being shadowed by the python26.dll in c:\Python26\. I have no idea
> > where that came from - as far as I know, I had a vanilla 2.6.2
> > installatio
> Yes, but what I experienced is much worse - I was actually getting the
> 2.6.2 version of python26.dll due to shadowing, instead of the 2.6.3
> version.
Ah. Did you get a message "[TARGETDIR] exists. Are you sure you want to
overwrite existing files?"
Regards,
Martin
___
On Sun, 04 Oct 2009 20:47:28 +0200, ""Martin v. Löwis""
said:
> > Yes, but what I experienced is much worse - I was actually getting the
> > 2.6.2 version of python26.dll due to shadowing, instead of the 2.6.3
> > version.
>
> Ah. Did you get a message "[TARGETDIR] exists. Are you sure you want
>>> Yes, but what I experienced is much worse - I was actually getting the
>>> 2.6.2 version of python26.dll due to shadowing, instead of the 2.6.3
>>> version.
>> Ah. Did you get a message "[TARGETDIR] exists. Are you sure you want to
>> overwrite existing files?"
>
> I may well have, but that wo
On Sun, 04 Oct 2009 21:42:29 +0200, ""Martin v. Löwis""
said:
> >>> Yes, but what I experienced is much worse - I was actually getting the
> >>> 2.6.2 version of python26.dll due to shadowing, instead of the 2.6.3
> >>> version.
> >> Ah. Did you get a message "[TARGETDIR] exists. Are you sure you
>> Ok, so I need to make the message more clear that this is an error, and
>> that most likely you do not want to proceed. If this was an upgrade
>> in place, the message would have read "This update will replace your
>> existing [ProductLine] installation."
>
> Well, I'm not at all sure that I sa
12 matches
Mail list logo
