Achievement unlocked
✅ Cause a `pip install` failure because the wheel build crosses a date boundary
Achievement unlocked
✅ Cause a `pip install` failure because the wheel build crosses a date boundary
I assume this happened because I have `dynamic = ["version"]` in my `pyproject.toml`, with the version computed by `versioningit` as a function of the current commit/tag, date, and working tree state.
Both `pip` and `setuptools` are resolving that, but with a delay between the two and if that delay happens to cross a date boundary, kaboom?
That makes sense to me but also seems like a flaw for dynamic versioning writ large…
Any #Python folks who have seen¹ this discrepancy in version between integration frontend and build backend have input? Is there some way to untie that TOCTOU-ish knot?
¹ no speculation, please, I am soliciting direct experience. I can generate plenty of speculation by myself.
If you have a fediverse account, you can quote this note from your own instance. Search https://hachyderm.io/users/SnoopJ/statuses/114393823987905958 on your instance and quote it. (Note that quoting is not supported in Mastodon.)