You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
`kernels init` prints suggested next steps after creating the project. A typical flow looks like:
48
48
49
49
```bash
50
-
cdmy_kernel
50
+
cdmy-kernel
51
51
cachix use huggingface
52
52
nix run -L --max-jobs 1 --cores 8 .#build-and-copy
53
53
uv run example.py
54
54
```
55
55
56
56
## Notes
57
57
58
-
- The `<repo>` part is normalized to lowercase, and `-` is replaced with `_`. For example, `my-user/My-Kernel` becomes a directory named `my_kernel` and a repo id `my-user/my_kernel`.
58
+
- The `<repo>` part is normalized to lowercase with dashes preferred. For example, `my-user/My_Kernel` becomes a directory named `my-kernel` and a repo id `my-user/my-kernel`.
59
+
- Python package names use underscores (e.g., `my_kernel`) since dashes are not valid in Python identifiers.
59
60
-`--backends` can be one of: `cpu`, `cuda`, `metal`, `rocm`, `xpu`, `npu`, or `all`.
60
61
- If the target directory already exists and is not empty, `kernels init` exits with an error unless `--overwrite` is set.
61
62
- The project is initialized as a Git repo (via `git init`) because Nix flakes require it.
0 commit comments