GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Create a separate WASI container · Issue #12 · python/cpython-devcontainers

Create a separate WASI container #12

New issue
Copy link
New issue
Copy link
Closed as not planned
Closed as not planned
Create a separate WASI container#12
Copy link
Assignees
brettcannon

Description

@brettcannon
brettcannon
opened on Sep 26, 2024
Issue body actions

It should make caching easier since the WASI toolchains will change more than the base dev container. It would also allow for https://github.com/python/cpython/tree/main/.devcontainer to have a separate WASI dev container which pre-builds everything.

Reacted by Erlend E. Aasland

Activity

  1. brettcannon
    self-assigned this
    on Sep 26, 2024
  2. brettcannon commented on Nov 15, 2024

    @brettcannon
    brettcannon
    on Nov 15, 2024
    MemberAuthor
    More actions

    If we don't use latest in the CPython repo then I think this idea actually isn't worth it as it will cause more work (at least for me) as I would then have to worry about pinning in this container and over in the CPython repo. I think I can still do a separate devcontainer in CPython by using a different command to run for the codespace pre-build.

  3. brettcannon commented on May 29, 2025

    @brettcannon
    brettcannon
    on May 29, 2025
    MemberAuthor
    More actions

    This might make builds somewhat faster by layering a base container and then WASI on top of it (see #8).

  4. brettcannon commented on Jun 4, 2025

    @brettcannon
    brettcannon
    on Jun 4, 2025
    MemberAuthor
    More actions

    I don't think this is worth the overhead right now as changing the base devcontainer would then require updating the WASI container unless we start using labels more (e.g. labeling a container image as meant for Python 3.15 or something).

  5. brettcannon commented on Jun 11, 2025

    @brettcannon
    brettcannon
    on Jun 11, 2025
    MemberAuthor
    More actions

    I asked for feedback on what people wanted for WASI and this didn't come up, so I'm not going to worry about it.

  6. brettcannon
    closed this as not plannedon Jun 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

  • @brettcannon
    brettcannon

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    You are visitor 01402503 — GeezerVison does not store the pages you look up.
    Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.