exercism / exercism/python

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

Aberta
#3,012 3 comentários 0 reações 0 responsáveis Ver no GitHub
discussion 💬
Linguagem predominante
Python
Estrelas
2.5k
Forks
1.5k
Métricas de merge de PRs
Nenhum PR com merge em 30d

Descrição

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.

Guia de contribuição

Abrir o guia de contribuição

Avaliação

Esta issue ainda não foi avaliada.

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.