pyunifiprotect VS build

Also, MANIFEST.in is not required. There is no such file in this project of mine. It is fully handled by the packing pipeline.

Hello! I am the current maintainer of the Python library pyunifiprotect. I have never made a post for the library on here before, but I figured it was finally time with the recent Backup CLI I started adding features to.

That is not correct. The option is just not exposed in the frontend on any of the official applications. I exposed the option in both the UniFi Protect CLI/library I made and it is exposed as service in Home Assistant as well.

"Privacy Mode" is basically a compute feature provided by pyunifiprotect, which is what Home Assistant uses. The switch in HA does exactly what I said in Protect terms:

But I do I have a WIP PR to get a Docker container up for people to use. https://github.com/briis/pyunifiprotect/pull/194. Unfortunately, it is pretty big (~700MB) because ffmpeg is a fat boy.

If you want to pair multiple doorbells, you can either use pyunifiprotect or Home Assistant.

I would recommend checking out https://github.com/briis/pyunifiprotect to see what’s available. Also if you want to download historical events you can use https://github.com/danielfernau/unifi-protect-video-downloader

OSS project we have a Container configuration for (for reference): https://github.com/briis/pyunifiprotect/blob/master/.devcontainer/devcontainer.json

If it's pure Python, the only packaging file you need is `pyproject.toml`. You can fill that file with packaging metadata per PEP 518 and PEP 621, including using modern build tooling like flit[1] for the build backend and build[2] for the frontend.

With that, you entire package build (for all distribution types) should be reducible to `python -m build`. Here's an example of a full project doing everything with just `pyproject.toml`[3] (FD: my project).

[1]: https://github.com/pypa/flit

[2]: https://github.com/pypa/build

[3]: https://github.com/pypa/pip-audit

RE the dislike of a "third-party tool", what do you mean by this? All the major tools for packaging in Python are under the PyPA, e.g. - twine - build - hatch

building wheels/sdists to upload or install: build

python3 setup.py sdist bdist_wheel - no need for an sdist when building wheels, also I'd recommend using pypa/build instead.

The first step is to turn the internal package into a wheel (a *.whl file). We can use the build tool for this purpose. After installing build with pip we can run it as follows:

Shouldn't https://github.com/pypa/build help? I don't think it has enough features yet but I was under the impression that was the distro solution.