[libcamera-devel] [RFC v1 5/7] py: Add 'nonblocking' argument to get_ready_requests()
Tomi Valkeinen
tomi.valkeinen at ideasonboard.com
Wed Jun 29 09:11:56 CEST 2022
On 28/06/2022 11:16, David Plowman wrote:
> Hi everyone
>
> Sorry for not taking part in this discussion rather more, and thanks
> to those who have! I think I was asked further back if I had an
> opinion, so let me try and explain how I see things.
>
> Actually I don't have any particularly strong opinions, other than
> that I want things to work and to be easy to use. And if they stopped
> changing, that would be nice too!!
Valid requests, but I think I can promise you only the first one =). The
easy-to-use would be nice, but as we've discussed, perhaps the core
bindings should be, well, core, which doesn't always equal easy to use.
And the third one... I'll try to keep backward compatibility when
possible (at least for a period of time), but that's just not always the
case.
> I was actually OK with the previous version where get_ready_requests
> was non-blocking, it's only the more recent version that causes me
> some trouble because I can't simply flush out any lurking requests
> after stopping the camera - because there might not be any and I will
> simply lock up the system.
The v2 series goes back to that, although the code behind is a bit
different.
Tomi
More information about the libcamera-devel
mailing list