Misleading exception raised when metadata not read
Bug #687373 reported by
Olivier Tilloy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyexiv2 |
Fix Released
|
Medium
|
Olivier Tilloy |
Bug Description
In the 0.1.x series, when trying to access the metadata of an image that had not been read() yet, an IOError with a relevant error message was raised.
The same behaviour is expected in the 0.2.x series, but instead an AttributeError with a misleading error message is raised.
Script to reproduce:
import pyexiv2
m = pyexiv2.
m.exif_keys
Expected result: IOError: Image metadata has not been read yet
Current result: AttributeError: 'NoneType' object has no attribute '_exifKeys'
Changed in pyexiv2: | |
status: | Confirmed → In Progress |
Changed in pyexiv2: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixed with revision 337 of the trunk.