Hi,
I just wanted to functionally test an XML-RPC view and saw that
currently those requests are hand crafted using http().
Wolfgang and I came up with a special transport for
xmlrpclib.ServerProxy as a wrapper to http() so you can use
from zope.app.testing.xmlrpc import ServerProxy
On Tuesday 19 September 2006 04:14, Christian Theune wrote:
I changed the publisher xmlrpc tests to use this utility now. This has
two meanings
1) Those tests now both test the XML-RPC testing utility and the publisher
2) Those tests now have a bit different semantics: Instead of comparing
Hi Adam, Jim
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Adam Groszer
Sent: Monday, September 11, 2006 4:27 PM
To: Jim Fulton
Cc: zope3-dev
Subject: Re[2]: [Zope3-dev] possible bug in zope.wfmc
Hello Jim,
My specific usecase is:
Hi
Stephan Richter wrote:
On Tuesday 19 September 2006 04:14, Christian Theune wrote:
I changed the publisher xmlrpc tests to use this utility now. This has
two meanings
1) Those tests now both test the XML-RPC testing utility and the publisher
2) Those tests now have a bit different
The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux zc-buildbot.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 7716
Blamelist: ctheune,jukart,shh
BUILD FAILED: failed test_2
sincerely,
-The Buildbot
Hi there,
I figured I'd let everyone here know that we'll be using the Python
distutils SIG mailing list for discussions on buildout itself in the
future. (Jim asked there and got a yes)
I think that's the distutils SIG mailing list a great place to engage
non-Zope developers as well, and
On Tuesday 19 September 2006 07:39, Martijn Faassen wrote:
I figured I'd let everyone here know that we'll be using the Python
distutils SIG mailing list for discussions on buildout itself in the
future. (Jim asked there and got a yes)
How is the traffic on that list?
Regards,
Stephan
--
Hi Roger,
Tuesday, September 19, 2006, 12:08:20 PM, you wrote:
Update - Final is guarded by review_result == 'accepted'
Update - Issue is guarded by transitionName == 'update_issue'
Update - Review is guarded by transitionName == 'update_review'
RI Is this (Update - Final) not a end
On 9/19/06, Stephan Richter [EMAIL PROTECTED] wrote:
This is perfectly fine. The exact XML was never of interest.
I think this is right for most cases. Sometimes it may be (especially
in the case of reported bugs and error handling), but I think that's
an unusual situation. Those cases can
Stephan Richter wrote:
On Tuesday 19 September 2006 07:39, Martijn Faassen wrote:
I figured I'd let everyone here know that we'll be using the Python
distutils SIG mailing list for discussions on buildout itself in the
future. (Jim asked there and got a yes)
How is the traffic on that list?
The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux zc-buildbot.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 7718
Blamelist: fdrake
BUILD FAILED: failed test_2
sincerely,
-The Buildbot
___
The Buildbot has detected a failed build of Zope3 trunk 2.4 FreeBSD tmiddleton.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 7718
Blamelist: fdrake
BUILD FAILED: failed test_2
sincerely,
-The Buildbot
___
The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux zc-buildbot.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 7719
Blamelist: fdrake
BUILD FAILED: failed test_2
sincerely,
-The Buildbot
___
The Buildbot has detected a failed build of Zope3 trunk 2.4 FreeBSD tmiddleton.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 7719
Blamelist: fdrake
BUILD FAILED: failed test
sincerely,
-The Buildbot
___
The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux zc-buildbot.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 7720
Blamelist: fdrake
BUILD FAILED: failed test_2
sincerely,
-The Buildbot
___
The Buildbot has detected a failed build of Zope3 trunk 2.4 FreeBSD tmiddleton.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 7720
Blamelist: fdrake
BUILD FAILED: failed test_2
sincerely,
-The Buildbot
___
The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux zc-buildbot.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 7731
Blamelist: alecm,fdrake,jim,srichter
BUILD FAILED: failed test_2
sincerely,
-The Buildbot
The Buildbot has detected a failed build of Zope3 trunk 2.4 FreeBSD tmiddleton.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 7731
Blamelist: alecm,fdrake,jim,srichter
BUILD FAILED: failed test_2
sincerely,
-The Buildbot
Hi All,
What's the difference between these two?
implementedBy is what I meant to use, by I braino'ed isImplementedBy
instead.
Rather than getting an AttributeError, I just got unexpected behaviour :-(
Any ideas?
Chris
--
Simplistix - Content Management, Zope Python Consulting
19 matches
Mail list logo
