Reid D McKenzie

Oh - no you're right. Looks like this is an elisp bug due to the type being returned in the nREPL transport.

+1, at present `env CONTAINER_VERSION=dev exo apply docker-compose.yaml` will produce something along the lines of `Error response from daemon: no such image foo::` rather than resolving the environment as `docker-compose`...

In order to solve this problem we settled on using a workspace rule we call `python_config`, which is able to use the `rctx` to inspect the building host and template...

Should close this out; see https://github.com/bazelbuild/rules_python/pull/723#issuecomment-1307664330 Ftr here's the solution I've been using happily for some time - - https://git.arrdem.com/arrdem/source/src/branch/trunk/tools/python/bzl_pytest_shim.py - https://git.arrdem.com/arrdem/source/src/branch/trunk/tools/python/defs.bzl#L37-L62

https://github.com/caseyduquettesc/rules_python_pytest this came up in the slack yesterday, leaving it here for posterity. I note with some amusement it's almost line-for-line what I invented for my repo and what we're...

This seems like a special case of the general gap between rules_go and rules_python wrt the `patches=` directive enabled by generating a static repository list.

We've wound up having to implement something like this. `tensorflow` has ah fragmented packaging, so we've wound up having to build a bunch of machinery so that `py_library` can recognize...

I think this would do what I want -- ``` [tool.ruff.lint.extend-per-file-ignores] "src/pytests/**/test_*.py" = ["F811"] "src/pytests/**/*_test.py" = ["F811"] ```

Hey folks, we've been running a patched `flower` specifically for this feature for a minute now. Is there anything we can do to support getting this merged in?

We've achieved a "good enough" implementation of this by independently doing what @zoidyzoidzoid suggested. We have a two-level local + s3 cache for the hash blobs produced by `bazel-diff`. A...