Python absolutely can run scripts in installation. Before pyproject.toml, arbitrary scripts were the only way to install a package. It's the reason PyPi.org doesn't show a dependency graph, as dependencies are declared in the Turing-complete setup.py.
Wrong. Wheels were available long before pyproject.toml, and you could instruct pip to only install from wheels. setup.py was needed to build the wheels, but the build step wasn’t a necessary part of installation and could be disabled. In that sense its role is similar to that of pre-publish build step of npm packages, unless wheels aren’t available.
ONVIF is the (now quite old, but still very relevant) standard for interfacing IP cameras locally on a network.
A cheap-but-performant ONVIF camera on an isolated VLAN (or a physically-isolated network; I won't tell anyone) can be a thing of beauty that is also completely unable to call home to some mothership in the clown.
I'm frankly very surprised that I don't see it mentioned here more often when discussions of cameras arise.
ONVIF and RTSP are different things.
ONVIF is a device and services discovery protocol
RTSP is a video streaming protocol.
ONVIF can be used to discover a camera on a network, query it for its RTSP URL, and facilitate a connection between a client service and the RTSP stream. But you can't stream video via "ONVIF".
I have also found that poor onvif implementations run as root and not as any other user. If you’re sending auth creds, better make sure you have something protecting them on the wire…
And profiles. There are many different feature sets in onvif and just because a camera has onvif logo or compatibility doesn’t mean it will play nice with your gear.
Not my experience. I've tried several such cameras and most of them are underpowered and suffer from very low fps or are fine when there's no movement but with movement the fps drops drastically essentially making the camera close to useless.
reply