starlette VS python-mss

Fast Execution: FastAPI is built on top of Starlette and Pydantic, making it one of the fastest Python frameworks for building APIs.

The framework's efficiency comes from its use of Starlette for building asynchronous web services and Pydantic for robust data validation and serialization, powered by Python's type hints. Pydantic has recently announced the official release of Pydantic V2 (June 2023), which is a ground-up rewrite that offers many new features and performance improvements, so make sure to be using that instead of V1.

Uvicorn + Starlette 8k requests/s

Starlette documentation

Same here, but without these weird utils it doesn't get any better.

I have 7 YoE with Django. Its great at so many things. You see some code, like middlewares, and immediately understand what's going on.

Now, we also have Starlette. The base of all new, fancy asgi libraries. Here's the base middleware class.

https://github.com/encode/starlette/blob/8d7a1cacfb3e1a30cbb...

In the last couple of years I heard 'we're running fastapi on production. Wanna join us?' so many times... but the reality is that it's still not suitable for prod. Who wants to work with a code like that if you have a readable, stable Django? I'm clueless.

Set up Starlette, a tool we'll use to make async requests

I never used websockets in FastAPI so I wouldn't know how to guide you more, but Middleware in Websockets are 100% supported by Starlette : https://github.com/encode/starlette/issues/641

Websockets are the way but I would not recommend django as it's still not fully async. I would go for other tools.

VidGear provides an easy-to-use, highly extensible, Multi-Threaded + Asyncio Framework on top of many state-of-the-art specialized libraries like OpenCV, FFmpeg, ZeroMQ, picamera, starlette, streamlink, pafy, pyscreenshot, aiortc and python-mss at its backend, and enable us to flexibly exploit their internal parameters and methods, while silently delivering robust error-handling and real-time performance.

I'm using a python library called mss https://github.com/BoboTiG/python-mss

You can use PyGetWindow to get the info of a window based on its name, and then use your screenshot library of choice to get that part of the screen (personally I use mss because it’s fast and cross-platform).

mss can do this efficiently and cross-platform. What’s the use-case?

That was one of the main reasons I made my library pythonic-cv - I had solved the problem once (not super well), and realised I was going to have to do it again repeatedly, and thought that was a waste of time. While I was at it I added some additional nice features like iterating over a camera/video stream, using a context manager to handle cleaning it up/releasing it afterwards, and convenient processing and threaded recording loops. I've recently also added mss integration so you can use your screen as a video input in the same way as a camera or video file.

You may also want to consider using mss for taking screenshots efficiently, which allows specifying the screen region you want when taking the screenshot. It has OpenCV/numpy support.

That error shouldn't be happening, and is most likely some kind of error in mss. If you haven't already, I'd suggest trying to update your mss (e.g. python3 -m pip install --upgrade mss, and if that doesn't help then you should create an Issue on the GitHub page, mentioning your OS and what you're doing that's causing that error.

If you’re after speed I’d recommend mss for screenshots/recording, and tesserocr instead of pytesseract (note in particular the OpenCV option.

Your blog post claims to do image preprocessing with pyautogui, but I couldn’t find any image processing steps? Also, if you’re only using pyautogui to take screenshots, you might want to look at a library like mss, which is more efficient and also has support for multiple monitors :-)