All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, Vipin Varghese <vipin.varghese@amd.com>
Subject: Re: [PATCH 3/3] doc: rewrite shell scripts in Python
Date: Sat, 2 Apr 2022 00:47:45 +0300	[thread overview]
Message-ID: <20220402004745.7b9d34dc@sovereign> (raw)
In-Reply-To: <YkcozNW6evfXjwNA@bricha3-MOBL.ger.corp.intel.com>

2022-04-01 17:31 (UTC+0100), Bruce Richardson:
> On Fri, Apr 01, 2022 at 12:28:30AM +0300, Dmitry Kozlyuk wrote:
[...]
> > +            if is_source or name == 'meson.meson.build':  
> 
> duplicate "meson."

Thanks!

> > +                path = os.path.join(root, name)
> > +                if is_source:
> > +                    sources.append(path)
> > +                print(path , end=' ', file=dep)
> > +
> > +sys.stdout = open(api_examples, 'w')  
> 
> While this is a literal translation of what is done in the .sh file, I
> wonder if, for consistency, in the python versions we should always either
> use stdout redirection or always use "file=" option to printing. Right now
> we have a mix of both.

I was wondering about this too.
Will change to "file=" (see also below) because explicit is better.

> > +print('/**')
> > +print('@page examples DPDK Example Programs')
> > +print()  
> 
> Is this additional print done deliberately for clarity vs just putting '\n'
> on previous line?

Yes. I think '''-string will be cleaner, especially with "file=".

  reply	other threads:[~2022-04-01 21:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-31 21:28 [PATCH 0/3] doc: build on Windows Dmitry Kozlyuk
2022-03-31 21:28 ` [PATCH 1/3] doc: simplify CSS customization for Doxygen Dmitry Kozlyuk
2022-03-31 21:28 ` [PATCH 2/3] doc: fix API index Markdown syntax Dmitry Kozlyuk
2022-03-31 21:28 ` [PATCH 3/3] doc: rewrite shell scripts in Python Dmitry Kozlyuk
2022-04-01 16:31   ` Bruce Richardson
2022-04-01 21:47     ` Dmitry Kozlyuk [this message]
2022-04-06 17:10 ` [PATCH v2 0/3] doc: build on Windows Dmitry Kozlyuk
2022-04-06 17:10   ` [PATCH v2 1/3] doc: simplify CSS customization for Doxygen Dmitry Kozlyuk
2022-04-06 17:10   ` [PATCH v2 2/3] doc: fix API index Markdown syntax Dmitry Kozlyuk
2022-04-06 17:10   ` [PATCH v2 3/3] doc: rewrite shell scripts in Python Dmitry Kozlyuk
2022-05-11  9:34   ` [PATCH v2 0/3] doc: build on Windows Varghese, Vipin
2022-05-11 10:56     ` Dmitry Kozlyuk
2022-06-01 10:47   ` Thomas Monjalon

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=20220402004745.7b9d34dc@sovereign \
    --to=dmitry.kozliuk@gmail.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=vipin.varghese@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.