[Error-Handling]: instructions are unclear, and wrong programs pass the tests

Open

#1,780 opened on May 14, 2019 11 comments 0 reactions 1 assignee View on GitHub

@BethanyG is already working on this.

Since Jun 16, 2021.

Assessment

This issue has not been assessed yet.

bug 🐛 smolder🍲

I just did the error-handling exercise, and had several issues:

It was unclear at first what to do with inputs. Looking at the tests, it seemed that trying to convert the input to int was the right thing to try, but this is not mentioned in the readme or the stubs.
The test for whether a method throws an exception will pass any error that might occur, not just if it's intentionally raised:

def handle_error_by_throwing_exception():
    raise "(╯°□°）╯︵ ┻━┻"  # Raising a string is a TypeError, but passes the test

When returning a tuple, which element should be the result and which one the status? What should the result element be when it fails? No suggestion
No mention of advantages or disadvantages of the different kinds of error handling, or what is idiomatic Python.

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.