Stephen Moore

even with `--test` it does the same thing ``` ╰─ docker run \ --rm \ -it \ --name builder \ --privileged \ -v $(pwd)/example:/data \ -v /var/run/docker.sock:/var/run/docker.sock:ro \ homeassistant/aarch64-builder \...

Hi, it seems even in github actions I have the same problem https://github.com/delfick/photons/commit/963696928d9de5ac04f324c4584a0c1de8375f21

It would be useful to be able to tell uv to prefer using asdf/pyenv discovery/installation if that's available rather than only python-build-standalone

sure, done https://github.com/astral-sh/uv/issues/7400 Thanks!

@emmettbutler on a related note, it seems the watchdog means every import ends up using importlib, which adds several frames for every import. We recently had an incident where production...

@P403n1x87 when I tried to work out what I'd lose from turning it off I looked at https://github.com/search?q=repo%3ADataDog%2Fdd-trace-py%20ModuleWatchdog.register&type=code It seems turning it off loses me * iast (which I don't...

Hi @The-Compiler :) > in a way that is confusing and inconsistent. I don't doubt that, do you have ideas of less confusing/inconsistent way of doing this? My immediate thoughts...

ah yeah, that certainly aligns with my immediate idea :)

I imagine the difference is that pytest-asyncio has required decorators from the beginning for everything that had the async keyword whereas I made different tradeoffs to make that not necessary....

I've ended up going with a solution that uses fixtures instead of decorators, https://github.com/delfick/alt-pytest-asyncio/pull/20