Yocto Project Documentation
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: YP docs mailing list <docs@lists.yoctoproject.org>
Subject: commands to do "pip install" in docs README file need enhancing
Date: Thu, 20 Aug 2026 07:20:35 -0400 (EDT)	[thread overview]
Message-ID: <959e65b6-e7eb-bcc3-992f-bed7276c8449@crashcourse.ca> (raw)

[-- Attachment #1: Type: text/plain, Size: 1522 bytes --]


  I just went through this with another Sphinx-based documentation
repo -- installation instructions that advise the reader to install
Python modules with "pip install" fail on my Debian 13 system with:


$ pip install sphinx-lint
error: externally-managed-environment

× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
    python3-xyz, where xyz is the package you are trying to
    install.

    If you wish to install a non-Debian-packaged Python package,
    create a virtual environment using python3 -m venv path/to/venv.
    Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
    sure you have python3-full installed.

    If you wish to install a non-Debian packaged Python application,
    it may be easiest to use pipx install xyz, which will manage a
    virtual environment for you. Make sure you have pipx installed.

    See /usr/share/doc/python3.13/README.venv for more information.

note: If you believe this is a mistake, please contact your Python
installation or OS distribution provider. You can override this, at
the risk of breaking your Python installation or OS, by passing
--break-system-packages.
hint: See PEP 668 for the detailed specification.


  Yes, there are solutions, such as using "pipx" instead of "pip", and
what have you, but it seems that the README file should be augmented
with an explanation as to how to deal with the above given that the
"pip install" commands are, in some cases, guaranteed to fail.

rday

             reply	other threads:[~2026-08-20 11:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20 11:20 Robert P. J. Day [this message]
2026-08-20 13:23 ` commands to do "pip install" in docs README file need enhancing tgamblin
2026-08-20 14:47   ` [docs] " Quentin Schulz
2026-08-20 14:58     ` Robert P. J. Day
2026-08-20 16:31       ` Quentin Schulz
2026-08-20 20:11         ` Robert P. J. Day
2026-08-20 20:44         ` Robert P. J. Day

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=959e65b6-e7eb-bcc3-992f-bed7276c8449@crashcourse.ca \
    --to=rpjday@crashcourse.ca \
    --cc=docs@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox