This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gvanrossum
Recipients Dmitrey, christian.heimes, gvanrossum, mlvanbie
Date 2008-01-31.23:57:38
SpamBayes Score 0.0218114
Marked as misclassified No
Message-id <>
In-reply-to <>
On Jan 31, 2008 2:54 PM, Michael Van Biesbrouck wrote:
> Why do people want to use copy and deepcopy?  I think that the issue is
> that Python is an imperative language that passes and copies references.
>  If a library function doesn't treat its arguments as const, horrible
> things could happen.  Compounding this, several standard operations
> (such as sort) operate in place, so if you want to use them then you
> need to make shallow copies at the very least.

I see the point for shallow copies. I just don't see the point for deep copies.

> When non-scalar types
> nest, the whole structure can be deepcopied or copy can be used
> repeatedly in a selective manner (with a high chance of bugs).

I don't understand the use case. I still think this comes primarily
from a lack of familiarity with how Python is typically used.
Date User Action Args
2008-01-31 23:57:40gvanrossumsetspambayes_score: 0.0218114 -> 0.0218114
recipients: + gvanrossum, christian.heimes, mlvanbie, Dmitrey
2008-01-31 23:57:39gvanrossumlinkissue1515 messages
2008-01-31 23:57:38gvanrossumcreate