exercism / exercism/python

[Clock] Review Test Cases and Discuss Structure and Objectives of Exercise

Abierto
#3,012 3 comentarios 0 reacciones 0 asignados Ver en GitHub
discussion 💬
Lenguaje dominante
Python
Estrellas
2.5k
Forks
1.5k
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

Filing this as a tracking issue and invitation to a discussion on revisions to this exercise.

The intent of `Clock` was to practice class customization and operator overloading via `dunder methods` in Python.
We've recently had quite a few changes, adding `__repr__` to the mix, as well as additional instructions and tests in support of that change. A few issues have now come up around it:

1. Issue #2926
2. Issue #3008

It feels like this exercise is overloaded. It especially has too many tests, and is perhaps not clear enough in its directions and hints as to what the student does or does not need to think about for their implementations.

Thoughts on rework/adjustment clarification strategies welcome here.

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.