Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Properly handle copy/deepcopy #2074

Closed
einarf opened this issue Apr 24, 2024 · 1 comment
Closed

Properly handle copy/deepcopy #2074

einarf opened this issue Apr 24, 2024 · 1 comment
Labels
bug

Comments

@einarf
Copy link
Member

einarf commented Apr 24, 2024

Some are using copy or deepcopy to clone arcade objects. Especially sprites. This can potentially add a lot of different bugs and weird issues. Possibly we can implement __copy__ and __deepcopy__ just raising an exception with a useful error message for now?
@einarf einarf added the bug label Apr 24, 2024
@pushfoo pushfoo mentioned this issue Apr 26, 2024
Merged
@einarf
Copy link
Member Author

einarf commented Apr 26, 2024

Fix merged

@einarf einarf closed this as completed Apr 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@einarf