RFC: realtime v2

[mansueli]

What kind of change does this PR introduce?

Bug fix, feature, docs update, ...

What is the current behavior?

Please link any relevant issues here.

What is the new behavior?

Feel free to include screenshots if it includes visual changes.

Additional context

Add any other context or screenshots.

[sourcery-ai]

Hey @mansueli - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟡 General issues: 1 issue found
• 🟡 Security: 1 issue found
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.}

[sourcery-ai]

issue (code-quality): Raise a specific error instead of the general Exception or BaseException (raise-specific-error)

Explanation

If a piece of code raises a specific exception type rather than the generic [`BaseException`](https://docs.python.org/3/library/exceptions.html#BaseException) or [`Exception`](https://docs.python.org/3/library/exceptions.html#Exception), the calling code can:

• get more information about what type of error it is
• define specific exception handling for it

This way, callers of the code can handle the error appropriately.

How can you solve this?

• Use one of the built-in exceptions of the standard library.
• Define your own error class that subclasses Exception.

So instead of having code raising Exception or BaseException like

if incorrect_input(value):
    raise Exception("The input is incorrect")

you can have code raising a specific error like

if incorrect_input(value):
    raise ValueError("The input is incorrect")

or

class IncorrectInputError(Exception):
    pass


if incorrect_input(value):
    raise IncorrectInputError("The input is incorrect")

[sourcery-ai]

issue (code-quality): We've found these issues:

• Swap if/else branches (swap-if-else-branches)
• Remove unnecessary else after guard condition (remove-unnecessary-else)

[silentworks]

@mansueli this PR will need to be updated as some other PRs got merged in which are now causing merge conflicts with this one.