Bug
code_sandboxes==1.0.10 on PyPI raises ValueError: Unknown sandbox variant: jupyter when calling Sandbox.create(variant="jupyter") or Sandbox.list_environments(variant="jupyter"), even though "jupyter" is exactly the value documented in the docstring and in the error message's own "Supported variants" list.
Root cause in the installed 1.0.10 wheel (code_sandboxes/base.py):
- line ~303:
elif variant_value == "jupyter_server": (imports .jupyter_server_sandbox)
- line ~330: error message still says
"Supported variants: eval, docker, jupyter, ..."
- same mismatch repeated in
list_environments around line ~387
So any caller passing the documented "jupyter" string falls through to the else branch.
Why I'm filing an issue and not a PR
I checked the public branches to write a fix, and the bug does not exist there:
main (commit fa5a2ab): already uses elif variant_value == "jupyter": and imports .jupyter_sandbox, consistent with the docstring and error message, with the same 8 variants (eval, docker, jupyter, datalayer, google_colab, kaggle, monty, modal) as the 1.0.10 error text.enh/jupyter and var/google-colab: neither matches the jupyter_server_sandbox module name or comparison found in the shipped wheel either.
So the source that produced the 1.0.10 wheel doesn't seem to correspond to any branch I could inspect — this looks like a packaging/release issue (wrong ref released) rather than a source bug to patch via PR.
Suggested fix
Re-cut a release from current main (which already has the correct "jupyter" handling), or investigate what ref the 1.0.10 build was actually taken from.
Repro
```python
from code_sandboxes.base import Sandbox
Sandbox.create(variant="jupyter")
ValueError: Unknown sandbox variant: jupyter. Supported variants: eval, docker, jupyter, datalayer, google_colab, kaggle, monty, modal
```
Installed via: uvx code-sandboxes==1.0.10 (or any resolver picking up latest, published 2026-08-20T13:28:35Z).
Bug
code_sandboxes==1.0.10on PyPI raisesValueError: Unknown sandbox variant: jupyterwhen callingSandbox.create(variant="jupyter")orSandbox.list_environments(variant="jupyter"), even though"jupyter"is exactly the value documented in the docstring and in the error message's own "Supported variants" list.Root cause in the installed 1.0.10 wheel (
code_sandboxes/base.py):elif variant_value == "jupyter_server":(imports.jupyter_server_sandbox)"Supported variants: eval, docker, jupyter, ..."list_environmentsaround line ~387So any caller passing the documented
"jupyter"string falls through to theelsebranch.Why I'm filing an issue and not a PR
I checked the public branches to write a fix, and the bug does not exist there:
main(commitfa5a2ab): already useselif variant_value == "jupyter":and imports.jupyter_sandbox, consistent with the docstring and error message, with the same 8 variants (eval, docker, jupyter, datalayer, google_colab, kaggle, monty, modal) as the 1.0.10 error text.enh/jupyterandvar/google-colab: neither matches thejupyter_server_sandboxmodule name or comparison found in the shipped wheel either.So the source that produced the 1.0.10 wheel doesn't seem to correspond to any branch I could inspect — this looks like a packaging/release issue (wrong ref released) rather than a source bug to patch via PR.
Suggested fix
Re-cut a release from current
main(which already has the correct"jupyter"handling), or investigate what ref the 1.0.10 build was actually taken from.Repro
```python
from code_sandboxes.base import Sandbox
Sandbox.create(variant="jupyter")
ValueError: Unknown sandbox variant: jupyter. Supported variants: eval, docker, jupyter, datalayer, google_colab, kaggle, monty, modal
```
Installed via:
uvx code-sandboxes==1.0.10(or any resolver picking up latest, published 2026-08-20T13:28:35Z).