[issue22305] Documentation on deepcopy's problems is misleading

2014-08-30 Thread Shailesh Hegde

New submission from Shailesh Hegde:

https://docs.python.org//library/copy.html

"Two problems often exist with deep copy operations that don’t exist with 
shallow copy operations:

Recursive objects (compound objects that, directly or indirectly, contain a 
reference to themselves) may cause a recursive loop.
Because deep copy copies everything it may copy too much, e.g., administrative 
data structures that should be shared even between copies."

I believe the last line in above paragraph is missing a 'not' ahead of 'be 
shared'. 

It should read:
"administrative data structures that should be not shared even between copies"

--
assignee: docs@python
components: Documentation
messages: 226123
nosy: docs@python, shlsh
priority: normal
severity: normal
status: open
title: Documentation on deepcopy's problems is misleading
versions: Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python 3.5

___
Python tracker 
<http://bugs.python.org/issue22305>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue22305] Documentation on deepcopy's problems is misleading

2014-08-30 Thread Shailesh Hegde

Shailesh Hegde added the comment:

Thanks.

"Because deep copy copies everything it may copy too much, e.g., administrative 
data structures that need to be shared even between copies, which may not be 
the desired goal."

helps me understand better.

--

___
Python tracker 
<http://bugs.python.org/issue22305>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com