Skip to content

Clarify which action images match the local Python and R environments #1568

@iaindillingham

Description

@iaindillingham

When working in a Codespace, @rose-higgins was getting different results when running a notebook in the local Python environment compared to the jupyter action image. The local Python environment gave correct results; the jupyter action image gave incorrect results.1

Changing from jupyter:latest to python:latest didn't help, but then we remembered that python:latest is the same as python:v1. The local Python environment is based on python:v2. Changing from jupyter:latest to python:v2 resolved the issue.

Whilst I don't think there's a fix as such, I think we should document this gotcha on the "How to troubleshoot common issues in GitHub Codespaces" page. Essentially, we should clarify that the local Python environment matches python:v2 and that in the case of the Python action image, "latest" is an unfortunate (yet deliberate) misnomer. We should also clarify that the local R environment matches r:latest and that in the case of the R action image, "latest" means latest.

Footnotes

  1. https://bennettoxford.slack.com/archives/C33TWNQ1J/p1720711750334619

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions