From d3bc7a6d8a9cd5c134351a9a5fe1e036af153a13 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?C=C3=A9dric=20Krier?= <ced@b2ck.com>
Date: Tue, 16 Apr 2013 15:19:25 +0200
Subject: [PATCH] No need to manage copy of one2many

Copy of one2many is correctly managed since changeset aec785ab8362 (1.2.0)

issue3142
review786002
(transplanted from 39c1466acf71ff37e35fea6faa00df10bf076c6f)
---
 party.py | 12 +-----------
 1 file changed, 1 insertion(+), 11 deletions(-)

diff --git a/party.py b/party.py
index 1694c99766..c1e0c6e22d 100644
--- a/party.py
+++ b/party.py
@@ -179,17 +179,7 @@ class Party(ModelSQL, ModelView):
             default = {}
         default = default.copy()
         default['code'] = None
-        default['addresses'] = None
-        new_parties = []
-        for party in parties:
-            new_party = super(Party, cls).copy(party, default=default)
-            Address.copy([x.id for x in new_party.addresses],
-                    default={
-                        'party': new_party.id,
-                        })
-            new_parties.append(new_party)
-
-        return new_parties
+        return super(Party, cls).copy(parties, default=default)
 
     @classmethod
     def search_rec_name(cls, name, clause):