Attention: cross post
We have run in an apparent BTrees bug (with the BTrees version
included in Zope 2.5.1).
We try to insert a value into an BTrees.OOBTree.OOBTree instance
with
tree[k]= v
and get an exceptions.KeyError on 13384379A0pfvqTmtEQ.
The code comes from Zope's
Tim has fixed lots of bugs in the BTrees code since 2.5.1. Also, there
were cases in the Transience implementation where I was iterating over
the .keys()/.items()/.values() of an OOBTree or IOBTree and also
mutating its contents, which is disastrous. Is this one of those cases?
On Fri,
Hi,
Is there something wrong with XML-RPC client and Zope 2.6.0 ?
Things that worked perfectly with Zope 2.5.1 don't work any more !
Even when I make a hello world Python script handler like
## Script (Python) xtest
##bind container=container
##bind context=context
##bind namespace=
##bind
[Dieter Maurer]
We have run in an apparent BTrees bug (with the BTrees version
included in Zope 2.5.1).
...
We will install the BTrees package from ZODB-3.2a1 and
see whether the problem disappears.
I will report back...
There are two new kinds of sanity checks you can make there:
1.
s = Server('http://localhost')
try:
s = Server('http://localhost/')
And read the xmlrpclib.py docs where it automatically appends RPC2 if
the url doesnt end in a slash.
--
Andy McKay
___
Zope-Dev maillist - [EMAIL PROTECTED]
Gilles Lenfant wrote at 2003-1-24 17:24 +0100:
...
from xmlrpclib import Server
s = Server('http://localhost')
Append / to your URL. I.e. use:
s = Server('http://localhost/')
again. Resource: RPC2\nPOST
The RC2 not found it an indication that you just specified
the
Guido van Rossum wrote:
If only it were that easy. Everybody wants no new features except
for the one feature they desperately want to have without upgrading to
the next feature release. :-(
Still, we're back to the situation where it's been weeks since the last release,
and there's nothing
Guido van Rossum wrote:
If only it were that easy. Everybody wants no new features except
for the one feature they desperately want to have without upgrading to
the next feature release. :-(
Still, we're back to the situation where it's been weeks since the
last release, and there's
