Thanks for the report Hobson, and for your attention to details :)
The example code in the module docstring for src/pyexiv2/__init__.py was never meant to be actually executed as doctests, which is the reason why it fails. As you found out, making it work reliably is not trivial and IMHO makes the code less readable, which is kind of a no-go as it’s supposed to be easy-to-read and understand example code.
The code base already contains a comprehensive battery of unit tests so I don’t think doctests are needed. I guess the easiest solution is to ensure the example code is not parsed as valid doctests.
Thanks for the report Hobson, and for your attention to details :)
The example code in the module docstring for src/pyexiv2/ __init_ _.py was never meant to be actually executed as doctests, which is the reason why it fails. As you found out, making it work reliably is not trivial and IMHO makes the code less readable, which is kind of a no-go as it’s supposed to be easy-to-read and understand example code.
The code base already contains a comprehensive battery of unit tests so I don’t think doctests are needed. I guess the easiest solution is to ensure the example code is not parsed as valid doctests.