We are also experiencing this issue and it is blocking a production release.

Workarround: Install setuptools < 78 and add --no-build-isolation flag to pip install

pip install 'setuptools<78'
pip install python-quickbooks --no-build-isolation

BUMP. This got me on a couple different package dependencies today.

Hello! Please feel free to use this forked repo for your deployments in the meantime: https://github.com/kolleno/python-quickbooks/

For example in poetry.toml :
python-quickbooks = { git = "https://github.com/kolleno/python-quickbooks/", branch = "master" }

Thanks so much to @romeroyonatan for pinpointing this issue and providing the work-around.

For anyone using uv, here's a working config for the workaround.

pyproject.toml:

[project]
...
dependencies = [
    # other project deps that can be built independently
]

[project.optional-dependencies]
build-quickbooks = [
    # see https://github.com/ej2/python-quickbooks/issues/383
    "setuptools<78",
]
quickbooks = [
    "python-quickbooks==0.9.11",
]

[tool.uv]
no-build-isolation-package = ["python-quickbooks"]

[build-system]
requires = ["hatchling"]
build-backend = "hatchling.build"

bash or workflow file:

uv sync --extra build-quickbooks
uv sync --extra quickbooks
uv run <your script or file>

Bump @ej2 ?