There's a story there: I first worked on it because we had a bunch (20~) docker images to build in parallel, and the goal was to "build them fast" (we succeeded: builds from scratch went from ~40 mins to ~15 mins when combined with multi-stage builds)

I suppose it's the same reason there's a python HTTP server of the same name

Do you have any concerns about giving it the same name as the web framework? Sanic is one of the more popular Python web frameworks with over 12k stars on GitHub. I would guess that a significant portion of your potential users already associate the name with that established project. I'm not trying to police the name or anything, but it seems likely to cause confusion.

In practice I've found it's not really a big deal, because if you google "sanic" neither this project nor that one shows up. My users will search "sanic tool" or "sanic build" and their users will search "sanic web" or "sanic python"

I guess it's sub-optimal that there are two projects with the same name, but I grew too used to typing "sanic build" over the years to seriously consider renaming it

I immediately thought of the web framework as well, but who knows what will happen if this tool takes off. It's good to see that you had at least considered it and recognized it was sub-optimal.

Concurrent builds alone make this worthwhile while developing.