Thanks for the proposals, I've added newest=false in the SetUp, as well as
ellipsis. This seems ok for the 0.6 branch, but not enough for the trunk.
Christophe
Benji York a écrit :
> On Mon, Aug 11, 2008 at 3:27 PM, Jim Fulton <[EMAIL PROTECTED]> wrote:
>> On Aug 11, 2008, at 5:17 AM, Chris With
On Mon, Aug 11, 2008 at 3:27 PM, Jim Fulton <[EMAIL PROTECTED]> wrote:
>
> On Aug 11, 2008, at 5:17 AM, Chris Withers wrote:
>
>> Christophe Combelles wrote:
>>> Is this change ok?
>>> It seems to solve the previous failures in the 3.4 kgs, and speeds
>>> up the test.
>>
>> I don't have a problem w
On Aug 11, 2008, at 5:17 AM, Chris Withers wrote:
> Christophe Combelles wrote:
>> Is this change ok?
>> It seems to solve the previous failures in the 3.4 kgs, and speeds
>> up the test.
>
> I don't have a problem with the change, but this damages the
> usefulness of README.txt as documentat
Christophe Combelles wrote:
Is this change ok?
It seems to solve the previous failures in the 3.4 kgs, and speeds up
the test.
I don't have a problem with the change, but this damages the usefulness
of README.txt as documentation.
As someone who's never used zope3recipes, I'm going to read
Previously Christophe Combelles wrote:
> Is this change ok?
> It seems to solve the previous failures in the 3.4 kgs, and speeds up the
> test.
To just prevent upgrades you can use 'newest = false'.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wig
Is this change ok?
It seems to solve the previous failures in the 3.4 kgs, and speeds up the test.
Log message for revision 89568:
Added offline=true to every test buildout to prevent unexpected (potentially
recursive) upgrade during tests
Changed:
U zc.zope3recipes/branches/0.6/zc/
