public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lbyqqwqqw689 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/31170] New: some improvements about python codes
Date: Fri, 15 Dec 2023 01:46:40 +0000	[thread overview]
Message-ID: <bug-31170-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=31170

            Bug ID: 31170
           Summary: some improvements about python codes
           Product: glibc
           Version: 2.40
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: lbyqqwqqw689 at gmail dot com
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---

In glibc/scripts/build-many-glibcs.py, I see many occurrences of ";"
such as return 'missing';/exit (1);   But semicolons are used only in atypical
situations in Python.
So I think those codes need some improvements.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

                 reply	other threads:[~2023-12-15  1:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-31170-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).