You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for the awesome python wrapper for v4l2!!!
I running into an issue when v4l2capture can not find a device at the specified path. I have a try/catch statement surrounding the opening of the video device in case the user specifies an incorrect path:
However, unexpectedly, python is immediately terminated as well, whether it be a program or python interactive shell. Is there a way to handle this such that the python shell or program is not immediately terminated?
Thanks!!
The text was updated successfully, but these errors were encountered:
Sorry, I have no time to work on this project for now. I have not seen the problem you describe, but I have not tried to use it like that either. Is the Python interpreter killed with a segfault or is it a normal exit?
I would also like to clarify that I did not originally create this library, I only added it to my GitHub because I wanted to make some changes to the upstream code which has been abandoned for some time: https://launchpad.net/python-v4l2-capture
The project was originally written by Fredrik Portström (I do not know him, only know his name from the homepage)
jcoffland
added a commit
to jcoffland/python-v4l2capture
that referenced
this issue
Sep 15, 2018
Dear Gerbart,
Thank you for the awesome python wrapper for v4l2!!!
I running into an issue when v4l2capture can not find a device at the specified path. I have a try/catch statement surrounding the opening of the video device in case the user specifies an incorrect path:
As one might expect, for an incorrect path an IOError is returned:
However, unexpectedly, python is immediately terminated as well, whether it be a program or python interactive shell. Is there a way to handle this such that the python shell or program is not immediately terminated?
Thanks!!
The text was updated successfully, but these errors were encountered: