Thanks, I used some of your methods and believe it is now
working.
I also did a lot of experiments, which I've needed to do,
investigating when references vs values are passed and
returned. Not as obvious as I thought.
Duncan Booth wrote:
> phil wrote:
>
>
>>
>>
>>>The deepcopy protocol does
> but you clearly haven't
> been getting the results from this forum that you expected.
>
Yes I have, this is a wonderful forum.
I was just providing more info due to more testing.
--
http://mail.python.org/mailman/listinfo/python-list
phil wrote:
> I posted the following yesterday and got no response
When you don't get as much of a response as you expected, you might
consider the advice here:
http://www.catb.org/~esr/faqs/smart-questions.html
Pointing you here is only meant to be helpful. If you don't feel the
advice applie
phil wrote:
>
>> The deepcopy protocol does allow you to specify how complicated
>> objects should be copied. Try defining __deepcopy__() in your objects
>> to just copy the reference to the Canvas object instead of the object
>> itself.
>
> I can't figure out from the docs what __deepcopy__
> The deepcopy protocol does allow you to specify how complicated objects
> should be copied. Try defining __deepcopy__() in your objects to just copy
> the reference to the Canvas object instead of the object itself.
I can't figure out from the docs what __deepcopy__ is or how it
works.
I h
phil wrote:
> It is frustrating to think that in a language like python
> there might be things which you can't make a copy of.
> That is bizarre enough to wonder about a deep flaw or
> hopefully I'm just doing something very wrong.
To be honest, it doesn't really surprise me that you cannot copy
I posted the following yesterday and got no response
and did some testing simplifying the circumstances
and it appears that deepcopy fails when the object
to be copied contains a reference to a Canvas Object.
Perhaps any Tkinter object, didn't get that far.
The problem arises because I have a geom
