layday
layday
It's probably 'cause pip is calling `[setuptools.build_meta.]get_requires_for_build_wheel` to ensure all build dependencies are satisfied prior to building the wheel, which in turn calls `setup.py egg_info` with your `--config-settings`, for which...
You might wish to look into migrating to `pyproject.toml`-based configuration, which wasn't available at the time when this issue was opened and which setuptools won't rewrite.
You could try creating a stubs-only package if that's easier, renaming `can_ada.pyi` to `can_ada-stubs/__init__.pyi` - see https://peps.python.org/pep-0561/#stub-only-packages.
It would appear #199 returns a stdlib (`importlib.metadata`) distribution which setuptools then attempts to operate on using the backport (`importlib_metadata`) and the two are incompatible on Python 3.8 and .9.
Has this issue actually been observed anywhere outside of a contrived test case? Build re-exposes setuptools without the prepare hook to test reading a project’s metadata from a wheel. Unless...
> @layday , what's your take on these guys? Mostly surprised their repos haven't been taken down yet. I think there’s better ways to access CF - https://github.com/layday/instawow/blob/300a01fafb9ec920ce61a1e0c596db81517f1893/src/instawow/_sources/cfcore.py#L242 should give...
Looking at the linked PR, I believe they are referring to the `project_wheel_metadata` function from `utils` which doesn't check dependencies.
Done in #940.
The version check is here: https://github.com/pypa/build/blob/5a3c5243a2135236f207da3a4b6401e1561f952d/src/build/env.py#L75