materialsproject / crystaltoolkit

Crystal Toolkit is a framework for building web apps for materials science and is currently powering the new Materials Project website.
https://docs.crystaltoolkit.org
Other
149 stars 59 forks source link

pip install error: #363

Open Charlie0450 opened 1 year ago

Charlie0450 commented 1 year ago

Hi, I'm trying to install it on jupterlab but failed with error. Here is the error message. Can you please check if there is a solution?

error: subprocess-exited-with-error

Building wheel for crystaltoolkit-extension (pyproject.toml) did not run successfully. exit code: 1

[147 lines of output] running bdist_wheel running jsdeps running handle_files running build running build_py creating build creating build\lib 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\qguo39\AppData\Local\Temp\pip-build-env-9y8_war3\overlay\Lib\site-packages\setuptools\command\build_py.py:201: _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\qguo39\AppData\Local\Temp\pip-build-env-9y8_war3\overlay\Lib\site-packages\setuptools\command\build_py.py:201: _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 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 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 creating build\bdist.win-amd64\wheel\crystaltoolkit_extension-0.6.0.data\data\share\jupyter creating build\bdist.win-amd64\wheel\crystaltoolkit_extension-0.6.0.data\data\share\jupyter\labextensions creating build\bdist.win-amd64\wheel\crystaltoolkit_extension-0.6.0.data\data\share\jupyter\labextensions\crystaltoolkit-extension creating build\bdist.win-amd64\wheel\crystaltoolkit_extension-0.6.0.data\data\share\jupyter\labextensions\crystaltoolkit-extension\static copying crystaltoolkit-extension\labextension\static\474.a2b8326fcfbbe3b6cb15.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\474.a2b8326fcfbbe3b6cb15.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 ERROR: Could not build wheels for crystaltoolkit-extension, which is required to install pyproject.toml-based projects

liaoyujie-798 commented 5 months ago

您好,请问这个问题您解决了吗

Yuziyue commented 5 months ago

您好,请问这个问题您解决了吗

我也遇到这个问题,不知道你是否解决了,很奇怪的是我在linux上没出现这个问题但是在windows上出现了