scikit-build does not work with setuptools>=64 in edit mode

[njzjz]

In setuptools 63, when installing with pip install -v -e ., CMake will be executed.

In 64 and 65, using the same command, CMake won't be executed during installation.

[njzjz]

A temporary solution is to set the environment variable:

export SETUPTOOLS_ENABLE_FEATURES="legacy-editable"

It looks like setuptools 64 changes the behavior of the editable mode.

[henryiii]

Yes, this was seen by @kratsg shortly after 64 was released. That's a fine workaround until we figure out what needs to be done to support the new editable mode. I'll be more familiar with what needs to be done after working on scikit_build_core for a while, so probably will focus there unless someone comes along sooner to do it.

[casperdcl]

running into the same problem.

Arrived here via pypa/setuptools#3550 <- pypa/setuptools#3488 <- AMYPAD/CuVec#25

[abravalheri]

Just in case anyone is looking into this problem, the documentation for custom build was updated in the v64 release: https://setuptools.pypa.io/en/latest/userguide/extension.html. Hopefully this is useful.

[0x2b3bfa0]

Additional links for #740 (comment)

• Improve docs and behavior of editable installs pypa/setuptools#3414 ¹
• setuptools.command.build.SubCommand documentation

Footnotes

1. Especially because of this change ↩

[henryiii]

I believe this requires implementing get_output and get_output_mapping. This is something the current scikit-build can't produce, since it delegates the build to CMake, and has no idea about what is going in and out. scikit-build-core, however, does know this (via requiring CMake 3.15+ and using the File API introduced in 3.15), so I think this will have to wait until scikit-build-core is ready.

Unless I'm mistaken, but I think that's what is required.