Hi,from http://docs.python.org/ref/objects.htm """Types affect almost all aspects of object behavior. Even the importance of object identity is affected in some sense: for immutable types, operations that compute new values may actually return a reference to any existing object with the same type a
On 10/31/06, Kent Johnson <[EMAIL PROTECTED]> wrote:
Premnath Sah wrote:> I would like to know how i can guarantee that a new immutable object is> infact a new object.>> Example:>> >>> a = 1> >>> b = 1
> >>> a is b> True>> is w
kages/SOAPpy/SOAPBuilder.py", line 294, in dumpmeth(obj, tag, typed, ns_map) File "/cv/vendor/lib/python2.4/site-packages/SOAPpy/SOAPBuilder.py", line 358, in dump_string
id = self.checkref(obj, tag, ns_map) File "/cv/vendor/lib/python2.4/site-packages/SOAPpy/SOAPBuilder.py", line 260, in checkrefraise RecursionError, "Cannot serialize recursive object"
SOAPpy.Errors.RecursionError: >>>-- With Regards,Premnath Sah T. H.
___
Tutor maillist - Tutor@python.org
http://mail.python.org/mailman/listinfo/tutor
, line 263, in call raise HTTPError(code, msg)SOAPpy.Errors.HTTPError: ###
Forcing the manual string concatenation lets you go on, but this is just asilly kludge around what is fundamentally a bad SOAPYpy bug.My current recom