Consider mentioning deep copies

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

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
64/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
documentation

调研方向

Read the Ch2 material on assignment and the Ch3 section introducing lists and mutable/immutable types; the issue also points to Ch7 examples with lists of dataframes. Decide where a deep-copy explanation best fits without overwhelming learners, then update the relevant lesson material. Done when the pitfall and when deep copies are useful are explained at an appropriate point in the course.

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

描述

How could the content be improved?

In Ch2 the learners are taught that if you define b = a, any subsequent changes to a do not affect b . This is true for immutable variables but not for all data types.

Then in Ch3 we start modifying objects in-place, and in Ch7 we end up with things like lists of dataframes (nested mutables!). So it would be useful to mention the need for deep copies at some point to avoid a common pitfall people may face when writing their own code.

A logical place might be in Ch3 when you start on lists and mutable/immutable types, but I worry it's too early in the course and will just be confusing

主要语言
HTML
星标
25
派生
65
PR 合并指标
30 天内没有已合并 PR

环境准备

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

从这里开始

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

LibraryCarpentry/lc-python-intro 的其他 Issue

查看 LibraryCarpentry/lc-python-intro 的全部 Issue

相似的 Issue

更多 Documentation Issue

把新 issue 发到你的邮箱

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