[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[pygame] Concerning copy

To: pygame-users@xxxxxxxx
Subject: [pygame] Concerning copy
From: Kevin Turner <darian@xxxxxxxxxxxxx>
Date: Sat, 22 Apr 2006 15:05:46 -0400
Delivered-to: archiver@seul.org
Delivered-to: pygame-users-outgoing@seul.org
Delivered-to: pygame-users@seul.org
Delivery-date: Sat, 22 Apr 2006 15:05:50 -0400
In-reply-to: <c3f69bf60604131048i20c779e6va2372688a1df452f@mail.gmail.com>
Reply-to: pygame-users@xxxxxxxx
Sender: owner-pygame-users@xxxxxxxx

Recently I encountered an issue where Python would, instead of creating a new object, instead reference the original one. Using copy.copy() is a solution, but I'd much rather be able to toggle off the weird referencing that Python has been using and make exceptions as necessary. Is there any way to do this?

-Kevin

Follow-Ups:
- Re: [pygame] Concerning copy
  - From: Brian Fisher
- Re: [pygame] Concerning copy
  - From: Nate Nichols
- Re: [pygame] Concerning copy
  - From: Nelson
- Re: [pygame] Concerning copy
  - From: Sami Hangaslammi
- Re: [pygame] Concerning copy
  - From: Terry Hancock

References:
- Re: [pygame] Reading input without pygame.display.set_mode()
  - From: Patrick Mullen

Prev by Author: Re: [pygame] Semi-Neophyte requires jerky animation assistance
Next by Author: [pygame] Comments System
Previous by thread: Re: [pygame] Reading input without pygame.display.set_mode()
Next by thread: Re: [pygame] Concerning copy
Index(es):
- Author
- Thread