Resolves #321. Keeping the second Node.delete(), because I'm pretty sure the first one was never called.
Here's a quick test, since writing a whole test for the actual fablib code would be a chore: running the below snippet with python test.py | uniq only produces delete #2. It appears that the second delete() method shadowed the first.
class Test:
def delete(self):
print("delete #1")
def delete(self):
print("delete #2")
for i in range(1000):
t = Test()
t.delete()
t = Test()
for i in range(1000):
t.delete()
Resolves #321. Keeping the second
Node.delete()
, because I'm pretty sure the first one was never called.Here's a quick test, since writing a whole test for the actual fablib code would be a chore: running the below snippet with
python test.py | uniq
only producesdelete #2
. It appears that the seconddelete()
method shadowed the first.