Am 25.11.2010 um 13:58 schrieb Zope Tests Summarizer:
> Summary of messages to the zope-tests list.
> Period Wed Nov 24 13:00:00 2010 UTC to Thu Nov 25 13:00:00 2010 UTC.
> There were 79 messages: 6 from Zope Tests, 4 from buildbot at pov.lt, 19 from
> buildbot at winbot.zope.org, 9 from ccomb at
Hi,
currently the ZTK tests on the trunk do not run successfully in a virtualenv.
The errors look like:
atom:trunk mac$ bin/test-ztk
Running test-ztk-zope.securitypolicy
test-ztk-zope.securitypolicy failed with:
Traceback (most recent call last):
File
"/Users/mac/Documents/tmp/zopetoolkit/tr
Lennart Regebro writes:
> OK, I've run out of steam for this run of trying to port zc.buildout
> to Python 3. I got pretty far, in fact. Of course, if we wait too
> long, somebody will make big changes, and all will be messy and the
> branch will rot and we might as well start over. :-) So I want
On Thu, Nov 25, 2010 at 19:10, Robert Niederreiter wrote:
> Hi Folks,
>
> Why does recent zc.recipe.cmmi sticks hardcoded to version < 1.5.0b1 of
> zc.buildout in setup.py?
Digging into the logs, I've found that the change is introduced in
this changeset:
http://svn.zope.org/zc.recipe.cmmi/trunk/
Hi Folks,
Why does recent zc.recipe.cmmi sticks hardcoded to version < 1.5.0b1 of
zc.buildout in setup.py?
Regards
Robert
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding!
OK, I've run out of steam for this run of trying to port zc.buildout
to Python 3. I got pretty far, in fact. Of course, if we wait too
long, somebody will make big changes, and all will be messy and the
branch will rot and we might as well start over. :-) So I want to
avoid that, and get some help
Summary of messages to the zope-tests list.
Period Wed Nov 24 13:00:00 2010 UTC to Thu Nov 25 13:00:00 2010 UTC.
There were 79 messages: 6 from Zope Tests, 4 from buildbot at pov.lt, 19 from
buildbot at winbot.zope.org, 9 from ccomb at free.fr, 41 from jdriessen at
thehealthagency.com.
Test fai
On 11/25/10 11:31 , Lennart Regebro wrote:
> Which style do you prefer? I'll make zope.hookable, zope.i18nmessage
> and zope.proxy use the same style if we can agree on one.
The second. #ifdefs in code make code hard to follow and tend to lead to
problems. FWIW the Linux kernel tree has a similar
I've been porting some zope.* modules that have C-extensions to Python
3, and with the C-preprocessor you have so many possibilities that I
get all confused. So I'd like some opinions. Or onions. Or something.
The big issue is the module definition, which is quite different in
Python 2 and Python
