AppleScript vs PhotoKit

[torarnv]

Is there a list of the remaining issues lack of feature parity between these two mechanisms of exporting photos? I would assume PhotoKit should be the more stable approach, given that it's a supported direct API, compared to controlling Photos.app via AppleScript, but perhaps that's not the case? What would it take to make PhotoKit be a stable (and preferred) export backend for osxphotos ? Thanks!

[RhetTbull]

I'd like to switch to PhotoKit and have a separate project to create a more robust PhotoKit interface but just haven't had time to complete this and test. Several users have said they've had issues with PhotoKit. I think most of these are due to the user not granting permission when the terminal first asks for permission to access Photos. If the user does that, future calls fail. But I've not been able to do enough testing with different configurations to figure this out.

Also, the current PhotoKit code doesn't provide a way to create albums which is a feature many users use. I plan to add this but again, haven't had the time.

[RhetTbull]

Thanks @torarnv I'll read up on these ideas. My ultimate goal is to figure out how to make your solution work with pyapp which would enable osxphotos to self update when there's a new version. PyApp creates an executable built in Rust that at first execution, downloads python and the osxphotos package then spawns a new process to run osxphotos. In subsequent runs, the previously installed python executable is spawned to run osxphotos. There's likely a way to make this work but it'll be several weeks before I have time to dive into PyApp internals.

[RhetTbull]

I think I've got this working for both pyinstaller and pyapp. Will need to do a new release before I can fully test it (pyapp pulls from PyPI to build the exe). I moved the disclaim() call to the main cli entry point and check at that time for pyinstaller / pyapp. This should allow osxphotos to work as it currently does (request permission through terminal) when called from python but to use the disclaim call when called from an executable.

[torarnv]

Awesome @RhetTbull ! Do you have the patch for pyapp that I can take a look at?

[RhetTbull]

I've got it on a separate branch at the moment. See new disclaim.py and where it's called in the cli here:

osxphotos/osxphotos/cli/cli.py

Lines 111 to 113 in 9333cf3

	if pyinstaller() or pyapp():
	# Running from executable, run disclaimer
	disclaim()

[torarnv]

Thanks! Look forward to testing it out!