[icanhasmath]

Problem

The AS Windows build of ingredient filelock 3.1.0.1 fails on windows-2025-msvc-builder:

Copying src\filelock.egg-info to build\...\filelock-0.0.0-py2.7.egg-info
Created wheel in ...\filelock-0.0.0-py2.py3-none-any.whl
Builder Error Message: Distribution name and/or version could not be determined.

0.0.0 is distutils' get_version() fallback for version is None. filelock 3.1.0 declares its version nowhere statically — it comes solely from setuptools_scm's finalize_distribution_options hook (infer_version), driven by [tool.setuptools_scm]. That hook does not run on this builder, and infer_version swallows every failure (except Exception: return trace_exception()), so the version silently stays None and ActiveStateWheel/steps.py rejects the resulting wheel.

Two things that do not fix it, both ruled out empirically:

• Shipping an sdist — we already do; the build consumes our filelock-3.1.0+security.1.tar.gz (sha256 a582574…, byte-identical to the release asset) with a correct root PKG-INFO. Plain setuptools never reads an sdist's PKG-INFO for the version; only setuptools_scm's PKG-INFO fallback parser does, and that lives behind the dead hook.
• SETUPTOOLS_SCM_PRETEND_VERSION — tried on build 2 (4ef58fcc, --env-var=SETUPTOOLS_SCM_PRETEND_VERSION=3.1.0). Still filelock-0.0.0. The env var is read inside _do_parse, which is also behind the hook.

Not filelock-specific: the pristine PyPI sdist of backports.functools_lru_cache 1.6.6 fails identically on the same builder image (8d62bf93), while an otherwise-identical Windows build of it succeeds (f11ceddc). Worth a platform ticket of its own — this breaks any setuptools_scm + pyproject-only package there.

Fix

One line: a static version in setup.cfg [metadata], which plain setuptools reads with no scm, no toml, and no cooperation from the builder.

setuptools_scm is deliberately kept in pyproject.toml — removing it also removes its git file-finder, which shrinks the sdist from 586KB to 8KB (dropping tests/, docs/, example/).

Verification

Rebuilt sdist, extracted with no .git, on 2.7.18:

condition	setup.py --version
setuptools_scm absent	3.1.0+security.1
setuptools_scm 5.0.2 active	3.1.0+security.1
scm active, toml unimportable	3.1.0+security.1

Both paths converge because scm's PKG-INFO fallback reads back the same string it wrote.

• Wheel built with no scm on the path: filelock-3.1.0+security.1-py2.py3-none-any.whl — clears the builder's parts[1] == "0.0.0" gate.
• filelock.__version__ == '3.1.0+security.1'; _is_reparse_point (CVE-2025-68146 fix) present.
• 25/25 tests pass on 2.7.18 — matches the release baseline.
• Sdist: 586086 B vs 585971 B, same 43 members.

No version change, no behaviour change: 3.1.0+security.1 is unaffected, as are the virtualenv pin, Jira DE-8131, and the CVE override rows.

🤖 Generated with Claude Code