[issue3043] Recursion bug in deepcopy

Facundo Batista <[EMAIL PROTECTED]> added the comment: Two weeks passed, closing it manually (see http://mail.python.org/pipermail/python-dev/2008-February/076992.html). -- nosy: +facundobatista status: pending -> closed ___ Python tracker <[EMAIL PRO

[issue3043] Recursion bug in deepcopy

Changes by Georg Brandl <[EMAIL PROTECTED]>: -- resolution: -> wont fix status: open -> pending ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3043] Recursion bug in deepcopy

Tyler Laing <[EMAIL PROTECTED]> added the comment: Same problem, even with new-style classes. Here, I'll show the function I use to generate the graph as well. class Vertex(object): def __init__(self, type): self.type = type self.color=-1 s

[issue3043] Recursion bug in deepcopy

Guilherme Polo <[EMAIL PROTECTED]> added the comment: This should have been fixed at 2.2, as long as you change your classes to new-style classes. If it still happens, post a sample code using your new code that uses new-style classes. -- nosy: +gpolo ___

[issue3043] Recursion bug in deepcopy

Tyler Laing <[EMAIL PROTECTED]> added the comment: Whoops, sorry, correction, when there are 100 vertexes and 500 edges. ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue3043] Recursion bug in deepcopy

New submission from Tyler Laing <[EMAIL PROTECTED]>: With the following code: class Vertex: def __init__(self, type): self.type = type self.color=-1 self.edges=[] class Edge: def __init__(self, V1, V2):