camera.py | Python module for projective camera model | Computer Vision library

Should I import it differently or is there another way?

No, the import is alright. It instructs python to go to the parent package (of the package the file you are running is in) there it will find another package called functions, then from there import set_camera. But as the error message says:

attempted relative import with no known parent package

python can't find the parent package to do the relative import. That parent package is not (and for technical reasons, like import hooks, can not be) the parent directory of the file you are running. For one, python would have to scan the whole filesystem to find possible packages. Instead, python scans the directory it's run from, in this case calibration finds no parent package (or indeed any package structure) and boom. So yes there is another way - give python the fully qualified name of the module you want to run. To do so you need to first rename the shoot-a-photo.py file to be a valid module name shoot_a_photo.py. Then cd to the parent directory of misc and use the -m switch:

The functionality of setting Process.daemon = True will cause the main process to call Process.terminate() when it exits. This is meant for long running child processes that can handle being closed without warning (in general you should handle the SIGTERM signal to cleanup before exiting).

Your main function in "launcher.py" does not wait for the child to do anything, and tries to exit basically right away. There seems to be just enough time for the child to get to the print("check 00") line before it's killed. This may seem somewhat consistent, but it should not be counted on even printing that. It's a race between how much the child can accomplish before the main process gets around to closing it.

Fixing this will depend on how you want it to function. If you still want the child to just run in the background forever until the main process exits, you need to make sure the main process takes some time (perhaps with time.sleep). If the child is completing some finite job, it probably shouldn't be a daemon, and you should call Process.join() on it to wait for it to finish at some point in main().

try this :

In order for everything to work correctly and the example below to run, you need to perform the following steps:

On your PC:

The absolutely simplest fix for your scenario is probably to have check.py monitor the file and restart the other process when necessary.

Solved this by creating an app context inside the model.py function. It turned out that for some reason mysql.connection is returning none.

If you have a studio/tools/__init__.py file like this:

Alright, so after several more test cases, a couple hours of research, and finally posting an issue on the PiCamera GitHub repo I finally figured it out. There is no direct documentation on this particular part of the PiCamera library as stated in my question. But someone on the repo was able to point me to the RaspiStill repo on adding GPS exif data, which is written in C. I've never completely learned C and my C++ skills are a bit rusty, but it gave me an idea. The end result came out to this:

...or at least an explanation of why gpiozero when_pressed is not playing nice.

My workaround was to have a private __capture() function, which acts as a wrapper to Clock.schedule_once(self.capture). capture_btn.when_pressed would use this private wrapper callback to avoid calling the problematic code directly, and any other uses of capture() would use the public one as normal since that works fine when not interacting with gpiozero.

In the following code I would prefer for capture() and __capture() to have swapped names since that would fit better with the philosophy of private functions, but unfortunately that's throwing AttributeError: 'RootWidget' object has no attribute '__capture' when I try that and I don't know how to fix that (using _RootWidget__capture isn't helping). The lines commented with ## illustrate my preferred but nonfunctional way.