Hello Stephan,
The most simple and 'brutal' way that I found is this:
def _stringify(string):
return string
import xmlrpclib
xmlrpclib._stringify = _stringify
What do you think about it?
Sunday, September 11, 2005, 4:26:34 PM, you wrote:
> On Wednesday 31 August 2005 09:23, Groszer Adam w
On Wednesday 31 August 2005 09:23, Groszer Adam wrote:
> Sorry, I'm a newbie regarding that. As I checked there is a
> zope.publisher.xmlrpc.premarshal_dispatch_table dict, but this is for
> the response. The request is handled 'directly' by xmlrpclib
> self._args, function = xmlrpclib.loads(self._
Hello Stephan,
Sorry, I'm a newbie regarding that. As I checked there is a
zope.publisher.xmlrpc.premarshal_dispatch_table dict, but this is for
the response. The request is handled 'directly' by xmlrpclib
self._args, function = xmlrpclib.loads(self._body_instream.read())
Can you please give a hin
On Tuesday 30 August 2005 11:55, Adam Groszer wrote:
> Is there any way to fool the Z3 XML-RPC publisher to unmarshall
> strings *always* as unicode? I think the problem is that xmlrpclib
> tries to convert all strings to str, but in Z3, all strings should be
> stored as unicode. Even better that z
On Tuesday 30 August 2005 11:55, Adam Groszer wrote:
> Is there any way to fool the Z3 XML-RPC publisher to unmarshall
> strings *always* as unicode? I think the problem is that xmlrpclib
> tries to convert all strings to str, but in Z3, all strings should be
> stored as unicode. Even better that z
Dear All,
Is there any way to fool the Z3 XML-RPC publisher to unmarshall
strings *always* as unicode? I think the problem is that xmlrpclib
tries to convert all strings to str, but in Z3, all strings should be
stored as unicode. Even better that zope.schema enforces unicode also.
So my exposed me
