Prabhu Ramachandran wrote:
"RD" == Robin Dunn writes:
>> >> On a Pycrust shell try something like this:
>> >> import Numeric a = Numeric.arange(0, 10, 0.001)
[...]
> Thanks. Have you by chance looked into what the effect of not
> doing the str(object) at all would be?
[...]
>> Nope. I just fixed the symptoms of the problem.
>>
>> Now that you mention it, *looking* at the code I guess one
>> could replace str(object) by str(type(object)) or
>> type(object).__name__. It looks like this is only used as a
>> key that has no other significance. It only needs to be
>> different from its __class__ and __bases__ which seems to hold
>> true always. This would avoid the str(object) problem
>> entirely. What do you think?> It sounds good to me but I don't know that code as well as I
> should. Go ahead and test it as much as you think is needed
> and then send me a patch and I'll play with it too.OK, I've played with a small patch somewhat but not extensively (I use
IPython more than pycrust). It seems to run just fine on all simple
tests I threw at it. I've attached it below (diff on the CVS
version).
Thanks. I'll give it a try.
···
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!