The-Strategy-Unit / The-Strategy-Unit/data_science
Write up Pydytuesday experiences
Open
@jacgrout is already working on this.
Since Jul 8, 2025.
section: blogs
- Dominant language
- Jupyter Notebook
- Stars
- 11
- Forks
- 5
- Avg merge
- 5h 34m
- Merged PRs (30d)
- 1
Description
@jacgrout, @anyaferguson and @Fikriyudin11 (supported by @tomjemmett) got together on 7 July to have a go at using Python to explore the latest Tidytuesday dataset (xkcd colour survey).
Would be nice to write this up. Maybe a generic intro and then a small subsection from each participant about their experience, what they learnt, how they overcome issues, etc. Possible angles:
- we're new(ish)-to-Python
- Tidytuesday gives a chance to practice on an unseen dataset
- the pydytuesday package helps import the Tidytuesday data into Python
- we used different writing tools (Google Colab, VS Code, Positron)
- uv and venv for environments/package management
- problems faced (e.g. pip not on PATH)
- conversation about differences between R and Python (e.g. the pipe)
- show code and plots
Contributor guide
No contributing guide indexed for this repository
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.
Assessment
This issue has not been assessed yet.