On 9/27/10, Sander Sweers <sander.swe...@gmail.com> wrote: > On 27 September 2010 23:15, Sander Sweers <sander.swe...@gmail.com> wrote: >>> objects: copying the memory location, not making a deep copy and >>> getting a duplicate object. >> >> It does not copy the object it makes multiple _references_ to the *same* >> object. > > Oops, You already got the idea and I should have read better. Ow well, > maybe the copy module was of interest to you. Yes, very much. I never even knew such a module existed, and I had wondered, through all of this, what would happen when a deep copy was required. Now I know. :) > > Greets > Sander >
-- Have a great day, Alex (msg sent from GMail website) mehg...@gmail.com; http://www.facebook.com/mehgcap _______________________________________________ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: http://mail.python.org/mailman/listinfo/tutor
