From: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
To: <newlib@sourceware.org>
Subject: Re: [PATCH 2/5] makedocbook: Use sys.exit()
Date: Fri, 4 Nov 2022 15:52:45 +0100 [thread overview]
Message-ID: <76169a71-250e-dbf7-73ef-9f2842b61a03@foss.st.com> (raw)
In-Reply-To: <20221104134946.13443-3-jon.turney@dronecode.org.uk>
Hi,
I'm no committer, so don't take my comment as such.
On 2022-11-04 14:49, Jon Turney wrote:
> Use sys.exit() to write a message to stderr and terminate with a
> non-zero exit code.
> ---
> newlib/doc/makedocbook.py | 16 ++++++----------
> 1 file changed, 6 insertions(+), 10 deletions(-)
>
> diff --git a/newlib/doc/makedocbook.py b/newlib/doc/makedocbook.py
> index 5e46082df..57cd23bfd 100755
> --- a/newlib/doc/makedocbook.py
> +++ b/newlib/doc/makedocbook.py
> @@ -214,8 +214,7 @@ def function(c, l):
>
> # FUNCTION implies starting a new refentry
> if refentry is not None:
> - print("multiple FUNCTIONs without NEWPAGE", file=sys.stderr)
> - exit(1)
> + sys.exit("multiple FUNCTIONs without NEWPAGE")
>
> # create the refentry
> refentry = lxml.etree.SubElement(rootelement, 'refentry')
> @@ -308,17 +307,15 @@ def synopsis(c, t):
>
> # a prototype without a terminating ';' is an error
> if s.endswith(')'):
> - print("'%s' missing terminating semicolon" % l, file=sys.stderr)
> + sys.exit("'%s' missing terminating semicolon" % l)
I'm not sure when it was introduced in python, but you can use this syntax:
sys.exit(f"'{l}' missing terminating semicolon")
If you don't want to use this fancy syntax, consider to at least do:
sys.exit("'%s' missing terminating semicolon" % (l,))
Kind regards,
Torbjörn
> s = s + ';'
> - exit(1)
>
> if ';' in s:
> synopsis_for_prototype(funcsynopsis, s)
> s = ''
>
> if s.strip():
> - print("surplus synopsis '%s'" % s, file=sys.stderr)
> - exit(1)
> + sys.exit("surplus synopsis '%s'" % s)
>
> def synopsis_for_prototype(funcsynopsis, s):
> s = s.strip()
> @@ -591,8 +588,7 @@ def t_eof(t):
>
> # Error handling rule
> def t_error(t):
> - print("tokenization error, remaining text '%s'" % t.value, file=sys.stderr)
> - exit(1)
> + sys.exit("tokenization error, remaining text '%s'" % t.value)
>
> lexer = lex.lex()
>
> @@ -795,8 +791,8 @@ def p_multitable(p):
> parser_verbose(p)
>
> def p_error(t):
> - print('parse error at line %d, token %s, next token %s' % (t.lineno, t, parser.token()), file=sys.stderr)
> - exit(1)
> + sys.exit('parse error at line %d, token %s, next token %s' % (t.lineno, t, parser.token()))
> +
>
> # protect creating the parser with a lockfile, so that when multiple processes
> # are running this script simultaneously, we don't get one of them generating a
next prev parent reply other threads:[~2022-11-04 14:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 13:49 [PATCH 0/5] makedocbook improvements (v2) Jon Turney
2022-11-04 13:49 ` [PATCH 1/5] makedocbook: Use raw strings for regexes Jon Turney
2022-11-04 13:49 ` [PATCH 2/5] makedocbook: Use sys.exit() Jon Turney
2022-11-04 14:52 ` Torbjorn SVENSSON [this message]
2022-11-05 14:28 ` Mike Frysinger
2022-11-04 13:49 ` [PATCH 3/5] makedocbook: Drop stray semicolons Jon Turney
2022-11-04 13:49 ` [PATCH 4/5] makedocbook: Adjust inline whitespace to fix flake8 warnings Jon Turney
2022-11-04 13:49 ` [PATCH 5/5] makedocbook: Fix false report of unhandled texinfo command Jon Turney
2022-11-05 14:28 ` [PATCH 0/5] makedocbook improvements (v2) Mike Frysinger
2022-11-07 8:48 ` Corinna Vinschen
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=76169a71-250e-dbf7-73ef-9f2842b61a03@foss.st.com \
--to=torbjorn.svensson@foss.st.com \
--cc=newlib@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).