opensafely-core / opensafely-core/opensafely-cli
Improve Python image handling of `jupyter` command
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 5
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 4
Description
From opensafely/documentation#1571, as flagged by @bloodearnest.
opensafely jupyter currently uses python:latest. We might want to explicitly specify python:v1 by default, and provide a way of specifying python:v2. We could also consider using python:v2 by default, although we'd have to be careful of the effect on existing users' work.
Allowing python:v2 would allow users to run notebooks
- with the newer Python image, including newer packages
- in Codespaces with the same version of Python packages as are locally installed
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.
Research direction
Start at the opensafely jupyter command and trace how its Python image is selected. Decide with maintainers whether python:v1 remains the default and how users request python:v2, accounting for existing users and Codespaces. Done means both image choices work and the default behavior is explicitly covered by the relevant CLI tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100