From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Kent Gibson <warthog618@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-gpio@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [libgpiod][PATCH 2/2] bindings: python: tests: set the process name
Date: Wed, 7 Dec 2022 12:57:02 +0200 [thread overview]
Message-ID: <Y5Bxftq6b6ENKD2R@smile.fi.intel.com> (raw)
In-Reply-To: <20221207091413.61616-2-brgl@bgdev.pl>
On Wed, Dec 07, 2022 at 10:14:13AM +0100, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
> When we run the test suite by calling the __main__ function of the module,
> the name of the process as visible in the system becomes "python". Let's
> set it to "python-gpiod" before running the tests. This way gpiosim will
> name its configfs attributes appropriately.
Perhaps you can refer to the [1] to explain why it's needed in Python.
Also it can be done via ctype module [2][3] or via module [4], although
I haven't checked if most used distros pack it.
[1]: https://bugs.python.org/issue5672
[2]: https://stackoverflow.com/a/923034
[3]: https://stackoverflow.com/a/31134436
[4]: https://github.com/dvarrazzo/py-setproctitle
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-12-07 10:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 9:14 [libgpiod][PATCH 1/2] gpiosim: get the process name using prctl() Bartosz Golaszewski
2022-12-07 9:14 ` [libgpiod][PATCH 2/2] bindings: python: tests: set the process name Bartosz Golaszewski
2022-12-07 10:57 ` Andy Shevchenko [this message]
2022-12-07 11:17 ` Bartosz Golaszewski
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=Y5Bxftq6b6ENKD2R@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=warthog618@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 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.