On May 4, 2010, at 6:07 AM, Martijn Faassen wrote:
> For a while already people have been making changes that at least break
> tests on 2.4. For instance, zope.testing has some facility to pretty print a
> dictionary that sorts the keys, because Python 2.4's built-in pretty print
> module appar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lennart Regebro wrote:
> On Mon, May 3, 2010 at 20:02, Tres Seaver wrote:
>> - - zope.browserpage
>> - - zope.viewlet
>> - - zope.contentprovider
>> - - zope.deferredimport
>
> These tests all fail because as Tres pointed out, Python 2.4 doesn't
> se
On Tue, May 4, 2010 at 12:07, Martijn Faassen wrote:
> For a while already people have been making changes that at least break
> tests on 2.4. For instance, zope.testing has some facility to pretty
> print a dictionary that sorts the keys, because Python 2.4's built-in
> pretty print module appare
Hanno Schlichting wrote:
> Dropping Python 2.4 supports makes most sense to me at this stage.
> Zope2/Plone only support Python 2.6 for any modern version.
>
> I don't know what BlueBream and Grok want to support, but would guess
> they aim for Python 2.5 + 2.6 support. 2.4 is really old by now.
Hi there,
Christophe Combelles wrote:
> Unless I missed something, the ZTK was globally compatible with Python2.4
> recently, wasn't it? Do we want the latest changes and Lennart's work to be
> part of the ZTK 1.0?
For a while already people have been making changes that at least break
tests
On Mon, May 3, 2010 at 20:02, Tres Seaver wrote:
> - - zope.browserpage
> - - zope.viewlet
> - - zope.contentprovider
> - - zope.deferredimport
These tests all fail because as Tres pointed out, Python 2.4 doesn't
set __file__ to the doctest filename in the globals. Zope.browserpage
in turn uses t
On Tue, May 4, 2010 at 00:41, Christophe Combelles wrote:
> Unless I missed something, the ZTK was globally compatible with Python2.4
> recently, wasn't it? Do we want the latest changes and Lennart's work to be
> part of the ZTK 1.0?
I think it's OK if they are not. Of course it would be cool i
On Tue, May 4, 2010 at 4:24 AM, Hanno Schlichting wrote:
> Dropping Python 2.4 supports makes most sense to me at this stage.
> Zope2/Plone only support Python 2.6 for any modern version.
>
> I don't know what BlueBream and Grok want to support, but would guess
> they aim for Python 2.5 + 2.6 supp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christophe Combelles wrote:
> Hanno Schlichting a écrit :
>> On Mon, May 3, 2010 at 8:02 PM, Tres Seaver wrote:
>>> Breakage in the following packages, but only on Python 2.4, and only in
>>> doctests:
>>>
>>> - - zope.browserpage
>>> - - zope.viewlet
On Tue, May 4, 2010 at 12:41 AM, Christophe Combelles wrote:
> Hanno Schlichting a écrit :
>> Hhm. I'm inclined to drop 2.4 support here. Using a zope.testing that
>> tries to be compatible all the way from 2.4 to 3.1 is quite a bit of a
>> stretch.
>
> Unless I missed something, the ZTK was globa
Hanno Schlichting a écrit :
> On Mon, May 3, 2010 at 8:02 PM, Tres Seaver wrote:
>> Breakage in the following packages, but only on Python 2.4, and only in
>> doctests:
>>
>> - - zope.browserpage
>> - - zope.viewlet
>> - - zope.contentprovider
>> - - zope.deferredimport
>>
>> At least the first on
On Mon, May 3, 2010 at 20:02, Tres Seaver wrote:
> At least the first one is due to doctests not exposing an '__file__' in
> their faux-module globals under 2.4. We might need to add Lennart's
> monkeypatch under 2.4, or else drop 2.4 support altogether.
Well, I don't want a monkey-patch product
Am 03.05.2010, 20:06 Uhr, schrieb Hanno Schlichting :
> Hhm. I'm inclined to drop 2.4 support here. Using a zope.testing that
> tries to be compatible all the way from 2.4 to 3.1 is quite a bit of a
> stretch.
+1
Python 2.4 itself is on life-support only*. I know it's an abrupt change
for anyo
On Mon, May 3, 2010 at 8:02 PM, Tres Seaver wrote:
> Breakage in the following packages, but only on Python 2.4, and only in
> doctests:
>
> - - zope.browserpage
> - - zope.viewlet
> - - zope.contentprovider
> - - zope.deferredimport
>
> At least the first one is due to doctests not exposing an '_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Test failures
> -
>
> Subject: FAILED: Repository policy check found errors in 670 projects
> From: ct at gocept.com
> Date: Sun May 2 21:17:48 EDT 2010
> URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014232.html
Expected br
15 matches
Mail list logo
