That’s an improvement for sure, but what would be really great is if the python bindings were either:
- packaged with the deepstream debian package (so it gets installed someplace global)
- pip installable via pypi or git, or a wheel, like Google does for Coral.
The problem for me is not so much moving pyds.so into a python path, but obtaining it in the first place. I get that maybe you want people to sign an agreement that they won’t use DeepStream for bad purposes, but people who will don’t care about such an agreement and making it more difficult to download things only frustrates everybody.
Right now, to get the bindings, one must go to the releases section of github, which redirects to a login wall, which leads to a download for one tarball, inside of which is another tarball, and so forth… It’s too many steps, and some of them can’t be taken (easily) in, say, a Dockerfile.
pip install is easy and “just works” on the other hand. The same I feel true for DeepStream itself. Version 4.0 is
apt-get installable, at least on Tegra. I hope the same will be true for 5.0 in time as well.