Summary of messages to the zope-tests list.
Period Thu Apr 30 12:00:00 2009 UTC to Fri May 1 12:00:00 2009 UTC.
There were 8 messages: 8 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.10 Python-2.4.6 : Linux
From: Zope Tests
Date: Thu Apr 30 20:45:18 EDT 2009
URL: http://
Martin Aspeli wrote:
> Your buildout is missing the [test] part.
Indeed, it's not supposed to be in the instance buildout, I was just
doing some testing ;-)
> I also had to create the log and var directories.
Yep, I'd imagine a downloadable "skeleton" for the instance which
included the folde
Andreas Jung wrote:
> We would have to maintain four different major release of Zope:
> 2.10, 2.11, 2.12 and 2.13.
Why? I suspect most of this work is caused by plohn.
If you're speaking as a member of that community, then fine, but that's
not really a Zope issue.
For me, I'd happilly just see Z
Hanno Schlichting wrote:
> Going back to the 3.4 stable set and being stuck at Python 2.4 would be
> quite disappointing for me.
Me too, especially as I now have a Zope 2.12 project that's using lots
of interesting Python 2.5'isms ;-)
Chris
--
Simplistix - Content Management, Zope & Python Con
Chris Withers wrote:
> plohn.
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org
On 01.05.2009 17:33 Uhr, Chris Withers wrote:
> Andreas Jung wrote:
>> We would have to maintain four different major release of Zope:
>> 2.10, 2.11, 2.12 and 2.13.
>
> Why? I suspect most of this work is caused by plohn.
> If you're speaking as a member of that community, then fine, but
> that's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 1, 2009, at 17:47 , Andreas Jung wrote:
> On 01.05.2009 17:33 Uhr, Chris Withers wrote:
>> Andreas Jung wrote:
>>> We would have to maintain four different major release of Zope:
>>> 2.10, 2.11, 2.12 and 2.13.
>>
>> Why? I suspect most of this
Hi all
The latest zope.testing is broken on windows.
It uses subprocess with a not supported argument
on windows (close_fds).
Traceback (most recent call last):
File "C:\Python25\lib\threading.py", line 486, in __bootstrap_inner
self.run()
File "C:\Python25\lib\threading.py", line 446, in
Jens Vagelpohl wrote:
> Chris, don't let personal grudges get in the way of planning decisions
> like this ;-)
Hey! Don't you go all good cop on me :-P
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
Hallo Roger,
Buildout was plagued also by this, solution is easy
see svn://svn.zope.org/repos/main/zc.buildout/trunk
r98303
Saturday, May 2, 2009, 1:12:39 AM, you wrote:
RI> Hi all
RI> The latest zope.testing is broken on windows.
RI> It uses subprocess with a not supported argument
RI> on win
10 matches
Mail list logo