From: zlice <zlice@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] pip wrong about installed packages
Date: Sat, 21 Oct 2023 22:47:43 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46821@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2174 bytes --]
New issue by zlice on void-packages repository
https://github.com/void-linux/void-packages/issues/46821
Description:
### Is this a new report?
Yes
### System Info
Void 6.5.7 x86_64 AuthenticAMD notuptodate rFFFFFFFFF
### Package(s) Affected
pip, python
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
pip detects proper packages and installs
### Actual behaviour
```
error: externally-managed-environment
× This environment is externally managed
╰─>
This system-wide Python installation is managed by the Void Linux package
manager, XBPS. Installation of Python packages from other sources is not
normally allowed.
To install a Python package not offered by Void Linux, consider using a virtual
environment, e.g.:
python3 -m venv /path/to/venv
/path/to/venv/pip install <package>
Appending the flag --system-site-packages to the first command will give the
virtual environment access to any Python package installed via XBPS.
Invoking python, pip, and executables installed by pip in /path/to/venv/bin
should automatically use the virtual environment. Alternatively, source its
activation script to add the environment to the command search path for a shell:
. /path/to/venv/activate
After activation, running
deactivate
will remove the environment from the search path without destroying it.
The XBPS package python3-pipx provides pipx, a convenient tool to automatically
manage virtual environments for individual Python applications.
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.
```
### Steps to reproduce
1. `xbps-install dlib`
2. `xbps-remove dlib`
3. `pip install dlib`
Did a `pip install dlib --break-system-packages` between 1 and 2 before remove, not sure if that matters
next reply other threads:[~2023-10-21 20:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-21 20:47 zlice [this message]
2023-10-21 20:58 ` classabbyamp
2023-10-21 21:38 ` [ISSUE] [CLOSED] " zlice
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46821@inbox.vuxu.org \
--to=zlice@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).