Zenika / Zenika/POEI-Python-Rss

Error message during pip install

Open
#3 2 comments 0 reactions 1 assignee View on GitHub

@Bullfrog666 is already working on this.

Since Apr 14, 2023.

Dominant language
Python
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

During pip install, I had the following error message

Collecting colorama
  Using cached colorama-0.4.6-py2.py3-none-any.whl (25 kB)
Installing collected packages: sgmllib3k, MarkupSafe, itsdangerous, feedparser, colorama, Werkzeug, Jinja2, click, Flask
  DEPRECATION: sgmllib3k is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
  Running setup.py install for sgmllib3k ... error
  error: subprocess-exited-with-error
  
  × Running setup.py install for sgmllib3k did not run successfully.
  │ exit code: 1
  ╰─> [11 lines of output]
      running install
      C:\Python311\Lib\site-packages\setuptools\command\install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
        warnings.warn(
      running build
      running build_py
      creating build
      creating build\lib
      copying sgmllib.py -> build\lib
      running install_lib
      byte-compiling C:\Python311\Lib\site-packages\sgmllib.py to sgmllib.cpython-311.pyc
      error: [Errno 13] Permission denied: 'C:\\Python311\\Lib\\site-packages\\__pycache__\\sgmllib.cpython-311.pyc.1506104212016'   
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure

× Encountered error while trying to install package.
╰─> sgmllib3k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.