All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ross Burton" <ross@burtonini.com>
To: "Zhang, Qiang" <qiang.zhang@windriver.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
	 OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] python3: use monotonic clock for condvar if possible
Date: Mon, 9 Aug 2021 18:53:14 +0100	[thread overview]
Message-ID: <CAAnfSTtD=Vz-3SY0UYBh62en9Z_WMzWP7iRQPynmJPmCR+PiHQ@mail.gmail.com> (raw)
In-Reply-To: <20210803051138.30790-1-qiang.zhang@windriver.com>

On Tue, 3 Aug 2021 at 05:41, Zhang, Qiang <qiang.zhang@windriver.com> wrote:
> The timeout for threading.Lock, threading.Condition, etc, is not using
> a monotonic clock, it is affected if the system time (realtime clock)
> is set.
>
> This patch will make condvar use monotonic clock.
> Refence: https://bugs.python.org/issue41710

That doesn't quite make sense to me.

As referenced in that bug report,
https://github.com/python/cpython/commit/001fee14e0f2ba5f41fb733adc69d5965925a094
uses monotonic clocks by default.  That was in 3.8.0 onwards.

So, why is this change to pretend that the semaphore is broken needed?

Ross

  parent reply	other threads:[~2021-08-09 17:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-03  5:11 [OE-core] [PATCH] python3: use monotonic clock for condvar if possible Zhang, Qiang
2021-08-09 15:45 ` Steve Sakoman
2021-08-09 17:53 ` Ross Burton [this message]
2021-08-11 11:36   ` Alexander Kanavin
2021-08-11 16:14     ` Mike Crowe
2021-08-11 16:32       ` Alexander Kanavin
2021-08-11 16:57         ` Mike Crowe

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='CAAnfSTtD=Vz-3SY0UYBh62en9Z_WMzWP7iRQPynmJPmCR+PiHQ@mail.gmail.com' \
    --to=ross@burtonini.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=qiang.zhang@windriver.com \
    --cc=richard.purdie@linuxfoundation.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 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.