Message139322
Amaury points out: this is not strictly about immutable objects, but rather objects who's deepcopy is themselves (identity-wise), in some (rare I think) cases this could provide a slowdown. Specifically a case of [(1, 2, 3)] * 10000 would be slower, because it would review each tuple individually, rather than using the memo'd instance. I suspect this case is not so common (to have the same identity object, who's deepcopy is itself such as a tuple or object with custom __deepcopy__, many times in a deepcopy object graph), but I have no proof of this. |
|
Date |
User |
Action |
Args |
2011-06-27 18:34:52 | alex | set | recipients:
+ alex, Carl.Friedrich.Bolz |
2011-06-27 18:34:52 | alex | set | messageid: <1309199692.5.0.142286089041.issue12422@psf.upfronthosting.co.za> |
2011-06-27 18:34:51 | alex | link | issue12422 messages |
2011-06-27 18:34:51 | alex | create | |
|