Remove redundant `Node.delete()`

[sajith]

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()

[coveralls]

Pull Request Test Coverage Report for Build 8978814744

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.008%) to 21.987%

---

Totals
Change from base Build 8883235255:	-0.008%
Covered Lines:	1159
Relevant Lines:	4697

---

💛 - Coveralls