exercism / exercism/python

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

Ouverte
#3,012 3 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
discussion 💬
Langage dominant
Python
Étoiles
2.5k
Forks
1.5k
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

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.

Guide de contribution

Ouvrir le guide de contribution

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.