Your message dated Sat, 12 Nov 2022 13:58:18 +0200
with message-id <[email protected]>
and subject line Re: Bug#1022151: python3-pip: Trying to install a package gave 
me some errors I believe are from pip.
has caused the Debian Bug report #1022151,
regarding python3-pip: Trying to install a package gave me some errors I 
believe are from pip.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1022151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022151
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python3-pip
Version: 20.3.4-4+deb11u1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: [email protected]

Dear Maintainer,

I was trying to install spotipy with:

pip3 install spotipy

and I got a wall of errors:

--- Logging error ---
Traceback (most recent call last):
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/utils/logging.py",
 line 177, in emit
    self.console.print(renderable, overflow="ignore", crop=False, style=style)
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_vendor/rich/console.py", 
line 1673, in print
    extend(render(renderable, render_options))
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_vendor/rich/console.py", 
line 1305, in render
    for render_output in iter_render:
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/utils/logging.py",
 line 134, in __rich_console__
    for line in lines:
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_vendor/rich/segment.py", 
line 249, in split_lines
    for segment in segments:
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_vendor/rich/console.py", 
line 1283, in render
    renderable = rich_cast(renderable)
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_vendor/rich/protocol.py",
 line 36, in rich_cast
    renderable = cast_method()
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/self_outdated_check.py",
 line 130, in __rich__
    pip_cmd = get_best_invocation_for_this_pip()
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/utils/entrypoints.py",
 line 58, in get_best_invocation_for_this_pip
    if found_executable and os.path.samefile(
  File "/usr/lib/python3.9/genericpath.py", line 101, in samefile
    s2 = os.stat(f2)
FileNotFoundError: [Errno 2] No such file or directory: '/usr/bin/pip3.9'
Call stack:
  File "/home/fabrice/.local/bin/pip3", line 8, in <module>
    sys.exit(main())
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/cli/main.py", 
line 70, in main
    return command.main(cmd_args)
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/cli/base_command.py",
 line 101, in main
    return self._main(args)
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/cli/base_command.py",
 line 223, in _main
    self.handle_pip_version_check(options)
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/cli/req_command.py",
 line 190, in handle_pip_version_check
    pip_self_version_check(session, options)
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/self_outdated_check.py",
 line 236, in pip_self_version_check
    logger.warning("[present-rich] %s", upgrade_prompt)
  File "/usr/lib/python3.9/logging/__init__.py", line 1454, in warning
    self._log(WARNING, msg, args, **kwargs)
  File "/usr/lib/python3.9/logging/__init__.py", line 1585, in _log
    self.handle(record)
  File "/usr/lib/python3.9/logging/__init__.py", line 1595, in handle
    self.callHandlers(record)
  File "/usr/lib/python3.9/logging/__init__.py", line 1657, in callHandlers
    hdlr.handle(record)
  File "/usr/lib/python3.9/logging/__init__.py", line 948, in handle
    self.emit(record)
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/utils/logging.py",
 line 179, in emit
    self.handleError(record)
Message: '[present-rich] %s'
Arguments: (UpgradePrompt(old='22.2.2', new='22.3'),)

This seamed like a pip error so I tryed 

pip3 install pip-install-test

And got a similar wall of errors:

Defaulting to user installation because normal site-packages is not writeable
Collecting pip-install-test
  Downloading pip_install_test-0.5-py3-none-any.whl (1.7 kB)
Installing collected packages: pip-install-test
Successfully installed pip-install-test-0.5
--- Logging error ---
Traceback (most recent call last):
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/utils/logging.py",
 line 177, in emit
    self.console.print(renderable, overflow="ignore", crop=False, style=style)
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_vendor/rich/console.py", 
line 1673, in print
    extend(render(renderable, render_options))
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_vendor/rich/console.py", 
line 1305, in render
    for render_output in iter_render:
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/utils/logging.py",
 line 134, in __rich_console__
    for line in lines:
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_vendor/rich/segment.py", 
line 249, in split_lines
    for segment in segments:
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_vendor/rich/console.py", 
line 1283, in render
    renderable = rich_cast(renderable)
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_vendor/rich/protocol.py",
 line 36, in rich_cast
    renderable = cast_method()
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/self_outdated_check.py",
 line 130, in __rich__
    pip_cmd = get_best_invocation_for_this_pip()
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/utils/entrypoints.py",
 line 58, in get_best_invocation_for_this_pip
    if found_executable and os.path.samefile(
  File "/usr/lib/python3.9/genericpath.py", line 101, in samefile
    s2 = os.stat(f2)
FileNotFoundError: [Errno 2] No such file or directory: '/usr/bin/pip3.9'
Call stack:
  File "/home/fabrice/.local/bin/pip3", line 8, in <module>
    sys.exit(main())
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/cli/main.py", 
line 70, in main
    return command.main(cmd_args)
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/cli/base_command.py",
 line 101, in main
    return self._main(args)
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/cli/base_command.py",
 line 223, in _main
    self.handle_pip_version_check(options)
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/cli/req_command.py",
 line 190, in handle_pip_version_check
    pip_self_version_check(session, options)
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/self_outdated_check.py",
 line 236, in pip_self_version_check
    logger.warning("[present-rich] %s", upgrade_prompt)
  File "/usr/lib/python3.9/logging/__init__.py", line 1454, in warning
    self._log(WARNING, msg, args, **kwargs)
  File "/usr/lib/python3.9/logging/__init__.py", line 1585, in _log
    self.handle(record)
  File "/usr/lib/python3.9/logging/__init__.py", line 1595, in handle
    self.callHandlers(record)
  File "/usr/lib/python3.9/logging/__init__.py", line 1657, in callHandlers
    hdlr.handle(record)
  File "/usr/lib/python3.9/logging/__init__.py", line 948, in handle
    self.emit(record)
  File 
"/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/utils/logging.py",
 line 179, in emit
    self.handleError(record)
Message: '[present-rich] %s'
Arguments: (UpgradePrompt(old='22.2.2', new='22.3'),)

My understanding is that it has something to do with path and I do not believe 
I've touched that and googling the issue other people seam to have this issue 
with Debian 11 such as : https://github.com/boltgolt/howdy/issues/598 

Their recommandation of simlinking the missing bin path seamed wrong as stock 
pip3 from debian. Also everything else python on my system seams to work 
without issues.

Thank you

-- System Information:
Debian Release: 11.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-18-amd64 (SMP w/12 CPU threads)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-pip depends on:
ii  ca-certificates     20210119
ii  python-pip-whl      20.3.4-4+deb11u1
ii  python3             3.9.2-3
ii  python3-distutils   3.9.2-1
ii  python3-setuptools  52.0.0-4
ii  python3-wheel       0.34.2-1

Versions of packages python3-pip recommends:
ii  build-essential  12.9
ii  python3-dev      3.9.2-3

python3-pip suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Hi Fabrice (2022.10.21_05:22:23_+0200)
> Dear Maintainer,
> 
> I was trying to install spotipy with:
> 
> pip3 install spotipy
> 
> and I got a wall of errors:
> 
> --- Logging error ---
> Traceback (most recent call last):
>   File 
> "/home/fabrice/.local/lib/python3.9/site-packages/pip/_internal/utils/logging.py",
>  line 177, in emit

Sorry, meant to send you a reply immediately, and promptly forgot.

That path is a locally installed version of pip, not the Debian pip
package. So, I'm closing the bug.

I don't think this bug is present in version 20.3.4-4+deb11u1, as
described. I can't reproduce it.

> My understanding is that it has something to do with path and I do not
> believe I've touched that and googling the issue other people seam to
> have this issue with Debian 11 such as :
> https://github.com/boltgolt/howdy/issues/598 

It's because you have a locally installed pip in
~/.local/lib/python3.9/site-packages that has a bug.
If you blow away ~/.local/lib/python3.9, and then re-install anything
you need, you can get back to a working system.

Not sure what's going on the bug that you referenced, but they all seem
like people who've got their systems into weird broken states that they
need to untangle.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

--- End Message ---

Reply via email to