Le 20/09/2010 17:19, Adam GROSZER a écrit :
> Hello Christophe,
>
> Monday, September 20, 2010, 4:53:16 PM, you wrote:
>
> CC> Le 19/09/2010 15:45, Marius Gedminas a écrit :
>>> On Sun, Sep 19, 2010 at 01:58:36PM +0200, Zope Tests Summarizer wrote:
Subject: FAILED : ZTK 1.0dev / Python2.5.5 L
On Tue, Sep 21, 2010 at 10:41 AM, Christophe Combelles wrote:
> This buildbot uses svn://svn.zope.org/repos/main/zopetoolkit/branches/1.0
> but in ZTK 1.0, the [source] section still points to the trunks, so it has no
> effect.
>
> We should now have a maintenance branch for ALL packages, and let
Le 21/09/2010 10:44, Hanno Schlichting a écrit :
> On Tue, Sep 21, 2010 at 10:41 AM, Christophe Combelles wrote:
>> This buildbot uses svn://svn.zope.org/repos/main/zopetoolkit/branches/1.0
>> but in ZTK 1.0, the [source] section still points to the trunks, so it has no
>> effect.
>>
>> We should
2010/9/21 Michael Howitz :
> Am 20.09.2010 um 17:22 schrieb Tres Seaver:
> [...]
>> Right, and we should be adding zope.testrunner to the ZTK trunk.
>
> Done in r116694. But this change might lead to other problems: When updating
> to zope.testing 3.10.0 in ztk-versions.cfg I get the following err
Summary of messages to the zope-tests list.
Period Mon Sep 20 12:00:00 2010 UTC to Tue Sep 21 12:00:00 2010 UTC.
There were 56 messages: 6 from Zope Tests, 4 from buildbot at pov.lt, 20 from
buildbot at winbot.zope.org, 14 from ccomb at free.fr, 12 from jdriessen at
thehealthagency.com.
Test fa
Am 21.09.2010 um 13:58 schrieb Gediminas Paulauskas:
> 2010/9/21 Michael Howitz :
>> Am 20.09.2010 um 17:22 schrieb Tres Seaver:
>> [...]
>>> Right, and we should be adding zope.testrunner to the ZTK trunk.
>>
>> Done in r116694. But this change might lead to other problems: When updating
>> to z
On Tue, Sep 21, 2010 at 3:39 PM, Michael Howitz wrote:
> @Hanno: Could you please decide in the ZTK release team, whether zope.testing
> 3.10 is a goal for the ZTK trunk. If so, I could merge the branch to the
> trunk and we could start fixing the tests. But maybe we should do this after
> the
Am 21.09.2010 um 13:58 schrieb Zope Tests Summarizer:
> Summary of messages to the zope-tests list.
> Period Mon Sep 20 12:00:00 2010 UTC to Tue Sep 21 12:00:00 2010 UTC.
> There were 56 messages: 6 from Zope Tests, 4 from buildbot at pov.lt, 20 from
> buildbot at winbot.zope.org, 14 from ccomb at
Hello Patrick,
Could you nag the buildbot maintainers to add an "svn info" step for
their bots?
The issue is that you can get the svn URL only from the bot config,
which is not always available.
--
Best regards,
Adam GROSZER mailto:agros...@gmail.com
--
Quote o
Hi All,
It's been a a while since I had a good rant on a Zope list, but this
really takes the biscuit.
Andreas, what on *earth* were you thinking with PreferredCharsetResolver?!
I like the idea of IUnicodeEncodingConflictResolver, but
PreferredCharsetResolver is in the realms of totally batshi
Am 21.09.2010, 20:17 Uhr, schrieb Chris Withers :
> To boot, when things go wrong, nobody suspects this miserable little
> turd because it's hides itself nicely by just returning the original
> text, leaving the bemused reader to wonder why some UA's fail and some
> succeed, pointing the finger in
On Tue, Sep 21, 2010 at 8:17 PM, Chris Withers wrote:
> I like the idea of IUnicodeEncodingConflictResolver, ...
[...]
> Why has no-one noticed this?
Because there's not all that many people left using plain Zope 2 and
upgrading to new versions.
The rest is using Plone, which has its own versi
On 21/09/2010 19:32, Hanno Schlichting wrote:
> Because there's not all that many people left using plain Zope 2 and
> upgrading to new versions.
Well, or they assume they must be doing something wrong because of this
default.
> The rest is using Plone, which has its own version of this:
>
> def
Am 21.09.2010, 20:39 Uhr, schrieb Chris Withers :
> So, would anyone object if I change the default, on both trunk and the
> 2.12 branch to some variant of:
> class BasicEncodingConflictResolver(object):
> implements(IUnicodeEncodingConflictResolver)
> def resolve(self, context, text, e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
First, cool down for a moment.
Second, I discussed all those issues with my special friend in some
Launchpad ticket years ago (+ a huge amount of private discussions).
I can not recall all details but at the time of the integration of the
Zope 3 ZPT e
On Tue, Sep 21, 2010 at 04:33:35PM +0200, Adam GROSZER wrote:
> Hello Patrick,
>
> Could you nag the buildbot maintainers to add an "svn info" step for
> their bots?
>
> The issue is that you can get the svn URL only from the bot config,
> which is not always available.
Patrick asked me
On Tue, Sep 21, 2010 at 07:39:46PM +0100, Chris Withers wrote:
> So, would anyone object if I change the default, on both trunk and the
> 2.12 branch to some variant of:
>
> class BasicEncodingConflictResolver(object):
> implements(IUnicodeEncodingConflictResolver)
>
> def resolve(se
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marius Gedminas wrote:
> On Tue, Sep 21, 2010 at 07:39:46PM +0100, Chris Withers wrote:
>> So, would anyone object if I change the default, on both trunk and the
>> 2.12 branch to some variant of:
>>
>> class BasicEncodingConflictResolver(object):
>>
Am 21.09.2010 um 15:43 schrieb Hanno Schlichting:
> On Tue, Sep 21, 2010 at 3:39 PM, Michael Howitz wrote:
>> @Hanno: Could you please decide in the ZTK release team, whether
>> zope.testing 3.10 is a goal for the ZTK trunk. If so, I could merge the
>> branch to the trunk and we could start fixi
19 matches
Mail list logo
