On Wed, 28 Mar 2012 07:29:18 -0400, Chris wrote:
Enrico,
On Tue, 27 Mar 2012 08:59:38 -0400, Chris wrote:
Did you try the patch mentioned in https://fedorahosted.org/suds/ticket/239?
Thanks for the pointer. I did try the patch but it doesn't change anything. While I receive the same exception "maximum recursion depth exceeded" as in the ticket, in my case it's caused at another place in the code. Suds parses my WSDL properly, it's just the pickling for caching which causes the exception :(.
From that same ticket, you may have seen an ugly hack that got me around a similar recursion bug -- https://fedorahosted.org/suds/ticket/239#comment:19
Yeah, I read it and also tried it, just forgot to tell about in my previous mail. Sorry.
Basically, just manually set the maximum recursion depth to something sufficiently high before calling Suds...
Values from 10000 on would do for my problem. Then the object is pickled and stored in the cache. Then it can be loaded from the cache and unpickled. But as you said, this is by no means a solution, not even a workaround.
If you want to experiment with some different limits, it might help you figure out if you're dealing with an infinite call chain or just a very deep one. In my case, the recursion depth seem to scale with the
Yes, that question raised also in my head though I didn't find time yet to look deeper into the recursion problem, will do soon, I hope.
The more interesting aspect of my first mail, for me, is rather the prefix generation/leaking problem as the simple memory cache would be good enough for me to not poke around with recursion errors while pickling.
Thanks, Enrico