v0.5.0

[sylikc]

Released to PyPI

Major refactor / rewrite of ExifTool. Lots of things changed. Check COMPATIBILITY.txt for more info.

While it is not directly backwards-compatible with v0.4.x, most use cases will only require minor changes to your existing code.

• Python 3.6+ required
• exiftool 12.15+ required

---

This discussion was created from the release v0.5.0.

[csparker247]

Just letting you know that I finally updated my code to use 0.5.2. The hardest thing was realizing that ExifTool.execute() takes str instead of byte strings now. Otherwise no problems!

[csparker247]

Beautiful!

[sylikc]

@csparker247 looks like I'm bringing back bytes ... apparently the change in v0.5.0 caused unintended side effects, which is ... like can't read bytes as per #47 ... and then there was also someone who posted that they can't read files which have mixed encodings...

I'm bringing in the best of both worlds... allow bytes and str in params to execute()... and return str by default, or bytes if requested

[csparker247]

Thanks for the heads up. I'll keep an eye out for that PR.

[sylikc]

Yeah there's a current PR active #48 but it's in draft right now so I can think more about whether it may cause unintended consequences itself.

Feel free to review that PR. The most interesting code you might be interested in is how to extract binary data with the new code 60d793f#diff-3e81514bd7e18cf47803b6172c9276fcc66e03967bd96cdb3d8a2db779ed9db1R30-R60

Another (relatively) big change is that ExifToolHelper() now allows passing in arbitrary types into execute, which allows something like this which wasn't allowed before:

et.execute("-SomeTag", Path.cwd() / "some file")

Which makes it easier... and oh, just reminded me that I can remove some checks in gettags and settags

[csparker247]

This seems alright for my purposes. I'm using ExifTool.execute(), so supporting Union[str, bytes] is sufficient for me. Thanks!