Closed mgorny closed 4 months ago
Encountered the same issue on a few of our internal builds this morning too. We use pyproject.toml
for configuring a suite of third party packages, but not for the project itself (still using setup.py
instead).
Our workaround was to pin to the previous version incremental==22.10.0
. Worth noting we also use towncrier
, which has an uncapped dependency on incremental
so that's how it got the latest version pulled in.
The command that triggered the same error for us was python setup.py bdist_wheel
, however some of our other builds which use the newer python -m build --wheel
command were unaffected.
Hmm, looking at the stripe setup.py it should be a no-op from Incremental's perspective. There is no use_incremental=True
opt-in. There is a pyproject.toml
with various tool configs which triggers this bug.
I'll put together a fix shortly.
Given this can potentially break the build of any setuptools-based project, generally causing havoc, I've yanked release 24.7.0 on PyPI so that folks don't automatically upgrade.
Thank you!
Thank you for the report! (And sorry for the breakage.)
After upgrading
incremental
to 24.7.0, various projects (that never used it) fail to build now, e.g.stripe
:In fact, I can't even build the previous version of
incremental
itself.