Zanie Blue
Zanie Blue
I can't seem to push to your branch, here are the edits I'd suggest: ```diff commit 72ed47cd2c4f2718628d2102521eda7805a6a534 (HEAD -> sinsniwal/main) Author: Zanie Blue Date: Mon Nov 24 16:13:28 2025 -0600...
Can we use this for the binary builds we use for integration tests too? Is there risk to using these fast builds for tests? Are we going to lose test...
I think some tools, e.g., tailscale(?), will detect the Homebrew case and actually just run the relevant Homebrew command for you. I'm not opposed but it won't be a high...
You'll probably need to define a [build system](https://docs.astral.sh/uv/concepts/projects/#build-systems) so your project is installed in the environment and discoverable by pytest.
I did some more reading here, and your case should work with: ``` ❯ uv run -m pytest ``` or ``` ❯ touch tests/__init__.py ❯ uv run pytest --pyargs my_module...
The problem is that, in Rust, there's a standardized test runner. In Python, there is not. We'd get complaints if we configured the project with pytest by default, though maybe...
In order for the library to be a proper Python module, it needs the directory to have the name. e.g., `/__init__.py`. Moving that directory into `src/` stops you from accidentally...
I don't think > Caused by: Permission denied (os error 13) Has anything to do with the GitHub token though, that's an error from your operating system. cc @Gankra
We can't do anything about GitHub rate limiting you, unfortunately. We'd need to host our artifacts elsewhere.
Thanks for the report!