Cached metadata is not converted to its correct type
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyexiv2 |
Fix Released
|
Low
|
Olivier Tilloy |
Bug Description
pyexiv2's internally cached metadata is not converted into the correct type although the data effectively written to the file is.
Here is an example interactive python session to reproduce:
------------
In [1]: import pyexiv2
In [2]: a = pyexiv2.
In [3]: a.readMetadata()
In [4]: a['Iptc.
Out[4]: ('3', '4')
In [5]: a['Iptc.
In [6]: a.writeMetadata()
In [7]: a.readMetadata()
In [8]: a['Iptc.
Out[8]: (5, 6)
In [9]:
Do you really want to exit ([y]/n)?
someone@
Python 2.5.1 (r251:54863, Oct 5 2007, 13:36:32)
[...]
In [1]: import pyexiv2
In [2]: a = pyexiv2.
In [3]: a.readMetadata()
In [4]: a['Iptc.
Out[4]: ('5', '6')
------------
Here the new multiple values of tag 'Iptc.Applicati
Changed in pyexiv2: | |
assignee: | nobody → osomon |
importance: | Undecided → Low |
status: | New → Confirmed |
description: | updated |
Changed in pyexiv2: | |
status: | Fix Committed → Fix Released |
Fix committed with revision 95.
The new value is now converted before being written to the internal metadata cache.
A unit test has been added to validate the fix.