raylu

it would be really helpful to mention this somewhere in the README

5874a3e3 nice. though I don't think the `__main` will work since you can't access double underscore prefixed symbols usually do you wanna package it up for pypi?

oh, apparently double underscore only applies to class members. it works fine, disregard me as for how to package, just add my `pyproject.toml` from the first comment, change `"dool:_main"` to...

you can do it yourself. there is no special list of trusted packagers for pypi. anyone can make a new package on pypi it is... conventional for the package maintainer...

I just remembered that pypi now has a whole fancy trusted publishers thing https://docs.pypi.org/trusted-publishers/ that lets you publish from a GH action https://github.com/marketplace/actions/pypi-publish so I made https://github.com/scottchiefbaker/dool/compare/next...raylu:dool:next which ran https://github.com/raylu/dool/actions/runs/8842864700...

oh nice! I was gonna manually publish 1.3.1, but that works too. also glad to see my thing actually worked, heh now that the package is created, do you want...

running with `--verbose` might help there was also a bug with relative paths that was fixed in uv 0.1.2: https://github.com/astral-sh/uv/issues/1393#issuecomment-1947772947

I was actually about to submit a PR for ```diff diff --git a/setup.py b/setup.py index 6d0fac7..11c07f8 100644 --- a/setup.py +++ b/setup.py @@ -22,10 +22,10 @@ setup( 'six==1.11.0' ], package_dir={"": "bin"},...

not sure if this is related or the same issue, but with ``` $ yapf --version yapf 0.32.0 ``` this works as expected ``` $ echo "def a(): return call(arg1,...

> Do coverage settings need to be per-test, or does a single build-wide config suffice? I would definitely settle for a single, build-wide config