[GH-ISSUE #2738] Installation error. #1026

New issue

Open

opened 2026-10-27 21:25:06 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-27 21:25:06 +00:00

Owner

Originally created by @rigin on GitHub (Mar 28, 2026).
Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/2738

PS H:\ComfyUI\custom_nodes\ComfyUI-Manager> pip install .
Processing ..
Installing build dependencies ... done
Getting requirements to build wheel ... error
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> [28 lines of output]
C:\Users\vadim\AppData\Local\Temp\pip-build-env-3mgd29uz\overlay\Lib\site-packages\setuptools\config_apply_pyprojecttoml.py:82: SetuptoolsDeprecationWarning: project.license as a TOML table is deprecated
!!

          ********************************************************************************
          Please use a simple string containing a SPDX expression for `project.license`. You can also use `project.license-files`. (Both options available on setuptools>=77.0.0).

          By 2027-Feb-18, you need to update your project and remove deprecated calls
          or your builds will no longer be supported.

          See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
          ********************************************************************************

  !!
    corresp(dist, value, root_dir)
  error: Multiple top-level packages discovered in a flat-layout: ['js', 'glob', 'misc', 'node_db', 'notebooks', 'snapshots', 'components'].

  To avoid accidental inclusion of unwanted files or directories,
  setuptools will not proceed with this build.

  If you are trying to create a single distribution with multiple packages
  on purpose, you should not rely on automatic discovery.
  Instead, consider the following options:

  1. set up custom discovery (`find` directive with `include` or `exclude`)
  2. use a `src-layout`
  3. explicitly set `py_modules` or `packages` with a list of names

  To find more information, look for "package discovery" on setuptools docs.
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed to build 'file:///H:/ComfyUI/custom_nodes/ComfyUI-Manager' when getting requirements to build wheel
PS H:\ComfyUI\custom_nodes\ComfyUI-Manager>

Originally created by @rigin on GitHub (Mar 28, 2026). Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/2738 PS H:\ComfyUI\custom_nodes\ComfyUI-Manager> pip install . Processing .\. Installing build dependencies ... done Getting requirements to build wheel ... error error: subprocess-exited-with-error × Getting requirements to build wheel did not run successfully. │ exit code: 1 ╰─> [28 lines of output] C:\Users\vadim\AppData\Local\Temp\pip-build-env-3mgd29uz\overlay\Lib\site-packages\setuptools\config\_apply_pyprojecttoml.py:82: SetuptoolsDeprecationWarning: `project.license` as a TOML table is deprecated !! ******************************************************************************** Please use a simple string containing a SPDX expression for `project.license`. You can also use `project.license-files`. (Both options available on setuptools>=77.0.0). By 2027-Feb-18, you need to update your project and remove deprecated calls or your builds will no longer be supported. See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! corresp(dist, value, root_dir) error: Multiple top-level packages discovered in a flat-layout: ['js', 'glob', 'misc', 'node_db', 'notebooks', 'snapshots', 'components']. To avoid accidental inclusion of unwanted files or directories, setuptools will not proceed with this build. If you are trying to create a single distribution with multiple packages on purpose, you should not rely on automatic discovery. Instead, consider the following options: 1. set up custom discovery (`find` directive with `include` or `exclude`) 2. use a `src-layout` 3. explicitly set `py_modules` or `packages` with a list of names To find more information, look for "package discovery" on setuptools docs. [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed to build 'file:///H:/ComfyUI/custom_nodes/ComfyUI-Manager' when getting requirements to build wheel PS H:\ComfyUI\custom_nodes\ComfyUI-Manager>

bsakaguchi commented

2026-10-27 21:25:07 +00:00

Author

Owner

@andreszs commented on GitHub (Apr 18, 2026):

This doesn’t really look like a normal Manager bug, it looks more like you’re mixing two different installation methods.

You’re running pip install . from inside custom_nodes/ComfyUI-Manager, which makes setuptools try to build that repo as a Python package, and that’s why you hit the “multiple top-level packages discovered” error. So it is related to ComfyUI-Manager, but not in the sense that the Manager UI or the registry is broken. It looks more like the current install instructions are easy to mix up, because the current docs say Manager is built into ComfyUI and should be enabled with --enable-manager after installing manager_requirements.txt, while the PyPI page also shows a pip install . method but only when the repo is cloned outside custom_nodes. I’d suggest just using the standard current setup with --enable-manager, or if you specifically want the pip route, clone the repo somewhere temporary outside custom_nodes and install it from there.

@andreszs commented on GitHub (Apr 18, 2026): This doesn’t really look like a normal Manager bug, it looks more like you’re mixing two different installation methods. You’re running `pip install .` from inside `custom_nodes/ComfyUI-Manager`, which makes setuptools try to build that repo as a Python package, and that’s why you hit the “multiple top-level packages discovered” error. So it is related to ComfyUI-Manager, but not in the sense that the Manager UI or the registry is broken. It looks more like the current install instructions are easy to mix up, because the current docs say Manager is built into ComfyUI and should be enabled with `--enable-manager` after installing `manager_requirements.txt`, while the PyPI page also shows a `pip install .` method but only when the repo is cloned outside `custom_nodes`. I’d suggest just using the standard current setup with `--enable-manager`, or if you specifically want the pip route, clone the repo somewhere temporary outside `custom_nodes` and install it from there.