From: lodger-c64 <lodger-c64@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Python 3.11.2_1 install throws "SyntaxError: invalid syntax" when byte-compiling /usr/lib/python3.11/site-packages/readability/compat/two.py
Date: Fri, 10 Feb 2023 10:23:41 +0100 [thread overview]
Message-ID: <20230210092341.df8gRBT0bCf_rkUvgrmyzmw8Slx8IXn00eZIJYkClZw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42178@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
Closed issue by lodger-c64 on void-packages repository
https://github.com/void-linux/void-packages/issues/42178
Description:
### Is this a new report?
Yes
### System Info
Void 6.1.10_1 x86_64 AuthenticAMD uptodate rrrmFFFFFFFFF
### Package(s) Affected
python3
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
Installation of Python 3.11 completes with all byte-compiles not throwing an error.
### Actual behaviour
When installing Python 3.11, there is an error when byte-compiling python site-packages:
[*] Configuring unpacked packages
python3-3.11.2_1: configuring ...
Byte-compiling python code in usr/lib/python3.11...
*** Error compiling './usr/lib/python3.11/site-packages/readability/compat/two.py'...
File "./usr/lib/python3.11/site-packages/readability/compat/two.py", line 6
raise exc_type(*args, **kwargs), None, traceback
^
SyntaxError: invalid syntax
Byte-compiling python3.11 code for module README.txt...
Updating ldconfig(8) cache...
python3-3.11.2_1: installed successfully.
### Steps to reproduce
I just need to run:
sudo xbps-install -f python3
next prev parent reply other threads:[~2023-02-10 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 9:13 [ISSUE] " lodger-c64
2023-02-10 9:23 ` lodger-c64 [this message]
2023-02-10 9:24 ` lodger-c64
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=20230210092341.df8gRBT0bCf_rkUvgrmyzmw8Slx8IXn00eZIJYkClZw@z \
--to=lodger-c64@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).