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

未关闭
#3,012 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
文档
描述清晰度
需要澄清
活跃度
停滞
技术栈
python

调研方向

首先检查 Clock exercise 当前的说明和测试,然后阅读关于所报告问题的 issues #2926 和 #3008。当该 exercise 的结构、目标、测试、说明和提示都有一份能够回应讨论的、已达成共识的修订计划时,即表示完成。

由索引模型根据 Issue 内容生成。

描述

discussion 💬

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.

主要语言
Python
星标
2.5k
派生
1.5k
平均合并
2 天 17 小时
30 天内合并 PR
2

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

exercism/python 的其他 Issue

查看 exercism/python 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。