From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Stefan Ring <stefanrin@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: gcc-commit-mklog fails
Date: Thu, 17 Nov 2022 10:35:18 +0000 [thread overview]
Message-ID: <CAH6eHdTu1pXG0PgFAFYjkBFPVVneF_aAHZxaEFtQB07JjVfVtQ@mail.gmail.com> (raw)
In-Reply-To: <CAAxjCEzYvXEHqeYfiRXzM0Ufc7N5vycJfgtTdmkxPhAuxf0BYA@mail.gmail.com>
On Thu, 17 Nov 2022 at 09:59, Stefan Ring via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
>
> On Thu, Nov 17, 2022 at 2:31 AM Zopolis0 via Gcc-help
> <gcc-help@gcc.gnu.org> wrote:
> >
> > Traceback (most recent call last):
> > File "/home/zopolis4/gcj/contrib/mklog.py", line 368, in <module>
> > output = generate_changelog(data, args.no_functions,
> > File "/home/zopolis4/gcj/contrib/mklog.py", line 165, in generate_changelog
> > diff = PatchSet(data)
> > File "/usr/lib/python3/dist-packages/unidiff/patch.py", line 460, in __init__
> > self._parse(data, encoding=encoding, metadata_only=metadata_only)
> > File "/usr/lib/python3/dist-packages/unidiff/patch.py", line 548, in _parse
> > current_file._parse_hunk(line, diff, encoding, metadata_only)
> > File "/usr/lib/python3/dist-packages/unidiff/patch.py", line 282, in
> > _parse_hunk
> > for diff_line_no, line in diff:
> > File "/usr/lib/python3.10/codecs.py", line 322, in decode
> > (result, consumed) = self._buffer_decode(data, self.errors, final)
> > UnicodeDecodeError: 'utf-8' codec can't decode byte 0xa0 in position
> > 3125: invalid start byte
> >
> > What should I do?
>
> Is it possible that the script was supposed to be executed by Python 2?
No. It is very clear about that:
#!/usr/bin/env python3
prev parent reply other threads:[~2022-11-17 10:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 1:30 Zopolis0
2022-11-17 9:08 ` Jonathan Wakely
2022-11-17 9:09 ` Jonathan Wakely
2022-11-17 9:57 ` Stefan Ring
2022-11-17 10:35 ` Jonathan Wakely [this message]
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=CAH6eHdTu1pXG0PgFAFYjkBFPVVneF_aAHZxaEFtQB07JjVfVtQ@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=stefanrin@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).