exercism / exercism/python

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

Abierto
#1,780 11 comentarios 0 reacciones 1 asignado Reclamado por @BethanyG Ver en GitHub
bug 🐛 smolder🍲
Lenguaje dominante
Python
Estrellas
2.5k
Forks
1.5k
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

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:
```python
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.

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.