Skip to content

[BUG] Codespaces devcontainer doesn't match local Python 3.12 / uv setup #61

Description

The devcontainer still uses mcr.microsoft.com/devcontainers/universal:2, a frozen Ubuntu 20.04 image that doesn't say which Python it ships, and installs with pip install --user -r requirements.txt. Since the move to pyproject.toml (requires-python >= 3.12) nothing guarantees a Codespace gets a Python that satisfies it, and the setup path diverges from the local one (uv sync --frozen). The README currently tells people not to use Codespaces (added in #25).

This blocks the CNG workshop on Oct 6 if anyone falls back to Codespaces during the session.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    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