Forums

: Could not build wheels for xmlsec which use PEP 517 and cannot be installed directly

.

(lamascadaeenv) 06:18 ~ $ pip install xmlsec
Looking in links: /usr/share/pip-wheels
Collecting xmlsec
  Using cached xmlsec-1.3.8.tar.gz (59 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Installing backend dependencies ... done
    Preparing wheel metadata ... done
Requirement already satisfied: lxml>=3.8 in ./.virtualenvs/lamascadaeenv/lib/python3.6/site-packages (from xmlsec) (4.5.2)
Building wheels for collected packages: xmlsec
  Building wheel for xmlsec (PEP 517) ... error
  ERROR: Command errored out with exit status 1:
   command: /home/paulpopaul/.virtualenvs/lamascadaeenv/bin/python3.6 /home/paulpopaul/.virtualenvs/lamascadaeenv/lib/python3.6/site-packages/pip/_vendor/pep517/_in_process.py build_wheel /tmp/tmphwndc_8g
       cwd: /tmp/pip-install-9dzjjlvn/xmlsec
  Complete output (14 lines):
  running bdist_wheel
  running build
  running build_py
  package init file 'src/xmlsec/__init__.py' not found (or not a regular file)
  creating build
  creating build/lib.linux-x86_64-3.6
  creating build/lib.linux-x86_64-3.6/xmlsec
  copying src/xmlsec/py.typed -> build/lib.linux-x86_64-3.6/xmlsec
  copying src/xmlsec/template.pyi -> build/lib.linux-x86_64-3.6/xmlsec
  copying src/xmlsec/constants.pyi -> build/lib.linux-x86_64-3.6/xmlsec
  copying src/xmlsec/tree.pyi -> build/lib.linux-x86_64-3.6/xmlsec
  copying src/xmlsec/__init__.pyi -> build/lib.linux-x86_64-3.6/xmlsec
  running build_ext
  error: xmlsec1 is not installed or not in path.
  ----------------------------------------
  ERROR: Failed building wheel for xmlsec
Failed to build xmlsec
ERROR: Could not build wheels for xmlsec which use PEP 517 and cannot be installed directly
(lamascadaeenv) 06:19 ~ $

I have this error to install Xmlsec

[edit by admin: formatting]

That's very strange -- it installed OK when I tried in a fresh Python 3.6 virtualenv just now, and your account has the same system image as mine.

Could you try creating a new virtualenv and seeing if it installs into that?