Failed to build installable wheels for some pyproject.toml based projects (crystaltoolkit-extension)

[hasandafa]

I installed the crystal toolkit library using
pip install crystal-toolkit
I found an error, also by using the git clone method or others as well but the error I met is still the same. Can anyone help me with the following error:

Building wheels for collected packages: crystaltoolkit-extension
  Building wheel for crystaltoolkit-extension (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Building wheel for crystaltoolkit-extension (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [154 lines of output]
      C:\Users\HP\AppData\Roaming\Python\Python310\site-packages\pip\_vendor\pyproject_hooks\_in_process\_in_process.py:251: _IncompatibleBdistWheel: wheel.bdist_wheel is deprecated, please import it from setuptools
      !!

              ********************************************************************************
              Ensure that any custom bdist_wheel implementation is a subclass of
              setuptools.command.bdist_wheel.bdist_wheel.

              By 2025-Oct-15, you need to update your project and remove deprecated calls
              or your builds will no longer be supported.

              See https://github.com/pypa/wheel/pull/631 for details.
              ********************************************************************************

      !!
        return _build_backend().build_wheel(wheel_directory, config_settings,
      running bdist_wheel
      running jsdeps
      running handle_files
      running build
      running build_py
      creating build\lib\crystaltoolkit-extension
      copying crystaltoolkit-extension\_version.py -> build\lib\crystaltoolkit-extension
      copying crystaltoolkit-extension\__init__.py -> build\lib\crystaltoolkit-extension
      running egg_info
      writing crystaltoolkit_extension.egg-info\PKG-INFO
      writing dependency_links to crystaltoolkit_extension.egg-info\dependency_links.txt
      writing requirements to crystaltoolkit_extension.egg-info\requires.txt
      writing top-level names to crystaltoolkit_extension.egg-info\top_level.txt
      reading manifest file 'crystaltoolkit_extension.egg-info\SOURCES.txt'
      reading manifest template 'MANIFEST.in'
      warning: no files found matching 'jupyter-config\crystaltoolkit-extension.json'
      no previously-included directories found matching '**\node_modules'
      no previously-included directories found matching 'lib'
      warning: no previously-included files matching '*~' found anywhere in distribution
      warning: no previously-included files matching '*.pyc' found anywhere in distribution
      warning: no previously-included files matching '*.pyo' found anywhere in distribution
      warning: no previously-included files matching '.git' found anywhere in distribution
      warning: no previously-included files matching '.ipynb_checkpoints' found anywhere in distribution
      adding license file 'LICENSE'
      writing manifest file 'crystaltoolkit_extension.egg-info\SOURCES.txt'
      C:\Users\HP\AppData\Local\Temp\pip-build-env-146c_5y8\overlay\Lib\site-packages\setuptools\command\build_py.py:220: _Warning: Package 'crystaltoolkit-extension.labextension' is absent from the `packages` configuration.
      !!

              ********************************************************************************
              ############################
              # Package would be ignored #
              ############################
              Python recognizes 'crystaltoolkit-extension.labextension' as an importable package[^1],
              but it is absent from setuptools' `packages` configuration.

              This leads to an ambiguous overall configuration. If you want to distribute this
              package, please make sure that 'crystaltoolkit-extension.labextension' is explicitly added
              to the `packages` configuration field.

              Alternatively, you can also rely on setuptools' discovery methods
              (for example by using `find_namespace_packages(...)`/`find_namespace:`
              instead of `find_packages(...)`/`find:`).

              You can read more about "package discovery" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

              If you don't want 'crystaltoolkit-extension.labextension' to be distributed and are
              already explicitly excluding 'crystaltoolkit-extension.labextension' via
              `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
              you can try to use `exclude_package_data`, or `include-package-data=False` in
              combination with a more fine grained `package-data` configuration.

              You can read more about "package data files" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


              [^1]: For Python, any directory (with suitable naming) can be imported,
                    even if it does not contain any `.py` files.
                    On the other hand, currently there is no concept of package data
                    directory, all directories are treated like packages.
              ********************************************************************************

      !!
        check.warn(importable)
      C:\Users\HP\AppData\Local\Temp\pip-build-env-146c_5y8\overlay\Lib\site-packages\setuptools\command\build_py.py:220: _Warning: Package 'crystaltoolkit-extension.labextension.static' is absent from the `packages` configuration.
      !!

              ********************************************************************************
              ############################
              # Package would be ignored #
              ############################
              Python recognizes 'crystaltoolkit-extension.labextension.static' as an importable package[^1],
              but it is absent from setuptools' `packages` configuration.

              This leads to an ambiguous overall configuration. If you want to distribute this
              package, please make sure that 'crystaltoolkit-extension.labextension.static' is explicitly added
              to the `packages` configuration field.

              Alternatively, you can also rely on setuptools' discovery methods
              (for example by using `find_namespace_packages(...)`/`find_namespace:`
              instead of `find_packages(...)`/`find:`).

              You can read more about "package discovery" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

              If you don't want 'crystaltoolkit-extension.labextension.static' to be distributed and are
              already explicitly excluding 'crystaltoolkit-extension.labextension.static' via
              `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
              you can try to use `exclude_package_data`, or `include-package-data=False` in
              combination with a more fine grained `package-data` configuration.

              You can read more about "package data files" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


              [^1]: For Python, any directory (with suitable naming) can be imported,
                    even if it does not contain any `.py` files.
                    On the other hand, currently there is no concept of package data
                    directory, all directories are treated like packages.
              ********************************************************************************

      !!
        check.warn(importable)
      creating build\lib\crystaltoolkit-extension\labextension
      copying crystaltoolkit-extension\labextension\package.json -> build\lib\crystaltoolkit-extension\labextension
      creating build\lib\crystaltoolkit-extension\labextension\static
      copying crystaltoolkit-extension\labextension\static\474.a2b8326fcfbbe3b6cb15.js -> build\lib\crystaltoolkit-extension\labextension\static
      copying crystaltoolkit-extension\labextension\static\474.a2b8326fcfbbe3b6cb15.js.LICENSE.txt -> build\lib\crystaltoolkit-extension\labextension\static
      copying crystaltoolkit-extension\labextension\static\534.e604f16025cd3727f855.js -> build\lib\crystaltoolkit-extension\labextension\static
      copying crystaltoolkit-extension\labextension\static\568.b028223ccaa16a3bf329.js -> build\lib\crystaltoolkit-extension\labextension\static
      copying crystaltoolkit-extension\labextension\static\598.d50a9e629232226aaef7.js -> build\lib\crystaltoolkit-extension\labextension\static
      copying crystaltoolkit-extension\labextension\static\remoteEntry.17e71a0669ae5bd364df.js -> build\lib\crystaltoolkit-extension\labextension\static
      copying crystaltoolkit-extension\labextension\static\style.js -> build\lib\crystaltoolkit-extension\labextension\static
      installing to build\bdist.win-amd64\wheel
      running install
      running install_lib
      creating build\bdist.win-amd64\wheel
      creating build\bdist.win-amd64\wheel\crystaltoolkit-extension
      creating build\bdist.win-amd64\wheel\crystaltoolkit-extension\labextension
      copying build\lib\crystaltoolkit-extension\labextension\package.json -> build\bdist.win-amd64\wheel\.\crystaltoolkit-extension\labextension
      creating build\bdist.win-amd64\wheel\crystaltoolkit-extension\labextension\static
      copying build\lib\crystaltoolkit-extension\labextension\static\474.a2b8326fcfbbe3b6cb15.js -> build\bdist.win-amd64\wheel\.\crystaltoolkit-extension\labextension\static
      copying build\lib\crystaltoolkit-extension\labextension\static\474.a2b8326fcfbbe3b6cb15.js.LICENSE.txt -> build\bdist.win-amd64\wheel\.\crystaltoolkit-extension\labextension\static
      copying build\lib\crystaltoolkit-extension\labextension\static\534.e604f16025cd3727f855.js -> build\bdist.win-amd64\wheel\.\crystaltoolkit-extension\labextension\static
      copying build\lib\crystaltoolkit-extension\labextension\static\568.b028223ccaa16a3bf329.js -> build\bdist.win-amd64\wheel\.\crystaltoolkit-extension\labextension\static
      copying build\lib\crystaltoolkit-extension\labextension\static\598.d50a9e629232226aaef7.js -> build\bdist.win-amd64\wheel\.\crystaltoolkit-extension\labextension\static
      copying build\lib\crystaltoolkit-extension\labextension\static\remoteEntry.17e71a0669ae5bd364df.js -> build\bdist.win-amd64\wheel\.\crystaltoolkit-extension\labextension\static
      copying build\lib\crystaltoolkit-extension\labextension\static\style.js -> build\bdist.win-amd64\wheel\.\crystaltoolkit-extension\labextension\static
      copying build\lib\crystaltoolkit-extension\_version.py -> build\bdist.win-amd64\wheel\.\crystaltoolkit-extension
      copying build\lib\crystaltoolkit-extension\__init__.py -> build\bdist.win-amd64\wheel\.\crystaltoolkit-extension
      running install_data
      creating build\bdist.win-amd64\wheel\crystaltoolkit_extension-0.6.0.data\data
      creating build\bdist.win-amd64\wheel\crystaltoolkit_extension-0.6.0.data\data\share\jupyter\labextensions\crystaltoolkit-extension\static
      copying crystaltoolkit-extension\labextension\static\568.b028223ccaa16a3bf329.js -> build\bdist.win-amd64\wheel\crystaltoolkit_extension-0.6.0.data\data\share\jupyter\labextensions\crystaltoolkit-extension\static
      error: could not create 'build\bdist.win-amd64\wheel\crystaltoolkit_extension-0.6.0.data\data\share\jupyter\labextensions\crystaltoolkit-extension\static\568.b028223ccaa16a3bf329.js': No such file or directory
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for crystaltoolkit-extension
Failed to build crystaltoolkit-extension
ERROR: ERROR: Failed to build installable wheels for some pyproject.toml based projects (crystaltoolkit-extension)

[webknjaz]

This last part is what's failing the build:

      creating build\bdist.win-amd64\wheel\crystaltoolkit_extension-0.6.0.data\data\share\jupyter\labextensions\crystaltoolkit-extension\static
      copying crystaltoolkit-extension\labextension\static\568.b028223ccaa16a3bf329.js -> build\bdist.win-amd64\wheel\crystaltoolkit_extension-0.6.0.data\data\share\jupyter\labextensions\crystaltoolkit-extension\static
      error: could not create 'build\bdist.win-amd64\wheel\crystaltoolkit_extension-0.6.0.data\data\share\jupyter\labextensions\crystaltoolkit-extension\static\568.b028223ccaa16a3bf329.js': No such file or directory

But I don't know why. It would be helpful to get a smaller reproducer (https://sscce.org). If it'd your project, try removing everything unnecessary from it until it works. This would help identify the culprit. Otherwise, report the issue upstream.

I see that they're using some cmdclass customizations: https://inspector.pypi.io/project/crystaltoolkit-extension/0.6.0/packages/57/be/6a7a1c209e164772bfb3a86a91a83fe04a2750204a6e4be5520c6f3beb74/crystaltoolkit-extension-0.6.0.tar.gz/crystaltoolkit-extension-0.6.0/setup.py#line.41. And those are coming from https://inspector.pypi.io/project/crystaltoolkit-extension/0.6.0/packages/57/be/6a7a1c209e164772bfb3a86a91a83fe04a2750204a6e4be5520c6f3beb74/crystaltoolkit-extension-0.6.0.tar.gz/crystaltoolkit-extension-0.6.0/pyproject.toml#line.2, which is pinned to an old version.

This is something that crystaltoolkit-extension maintainers must address. It would also be a good idea to get them to publish wheels — this way, building wouldn't be happening on your machine to begin with.