Reducing "read in" jargon
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- pandas, python
- Domain
- documentation
Research direction
Start in the "Combining DataFrames with Pandas" episode and search its code comments for uses of "read in" that describe subsetting rather than loading data. Update those comments with unambiguous wording, then review the episode to confirm every subsetting reference is clear to learners.
Written by the indexing model from the issue text.
Description
How could the content be improved?
At several places in the "Combining DataFrames with Pandas" episode, the code comments use "read in" to describe subsetting data. This could be confusing to learners, who would be familiar with "reading" as loading in data from, e.g., a csv (the read_csv command). I would suggest that instances of "read in" which refer to subsetting be re-worded. Example alternatives: "Subset first ten lines of surveys table" or "Save first ten lines of surveys table as a new object."
Which part of the content does your suggestion apply to?
No response
- Dominant language
- Jupyter Notebook
- Stars
- 176
- Forks
- 316
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from datacarpentry/python-ecology-lesson
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
All issues in datacarpentry/python-ecology-lesson
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100