exercism / exercism/python

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

Open
#3,012 3 comments 0 reactions 0 assignees View on GitHub
discussion 💬
Dominant language
Python
Stars
2.5k
Forks
1.5k
PR merge metrics
No merged PRs in 30d

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.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.