pyexiv2-developers team mailing list archive

[Damien Moore <damienlmoore@xxxxxxxxx>]

Ignore my last question, I just copied the libexiv2python.so to src/pyexiv2
and I can run the samples fine.

I'm going to start porting phraymd across to the new version over the next
week or so. Will let you know what issues come up.

On Sat, Feb 13, 2010 at 10:14 AM, Damien Moore <damienlmoore@xxxxxxxxx>wrote:

> Hi Olivier,
>
> pyexiv2 compiles with no problems for me (I had to apt-get install
> libexiv2-dev and libboost-python-dev). Now on to testing, but before I do
> that, can you suggest an easy way to install this version side by side with
> the 0.1 package? Ideally, I want to have them both available on this system.
>
> cheers,
> Damien
>
>
> On Mon, Jan 25, 2010 at 5:15 PM, Olivier Tilloy <olivier@xxxxxxxxxx>wrote:
>
>> Hello pyexiv2 users and developers!
>>
>> I'm pleased to announce that I now consider pyexiv2 0.2 (development
>> branch) complete and stable enough to start pre-release testing.
>>
>> Your help in making sure that this version matches your expectations is
>> greatly appreciated. I myself tested it quite extensively but I surely miss
>> a lot of use cases, and I would like to hear about your experience with it.
>> In particular, I'm interested in checking that:
>>
>>  - there are no regressions compared to the previous version (0.1.3)
>>  - known bugs and limitations with 0.1.3 are fixed in this version
>>
>> Since 0.2 is mostly a complete rewrite, a lot has changed, and the API is
>> _not_ backward compatible with the 0.1 series. This means that your scripts
>> and programs will need some adaptations to use the new version. The good
>> news is that this new version gives you access to more information
>> (including the long-awaited XMP metadata).
>>
>> The API is partly documented, and one of my goals for this release is to
>> have it fully documented (that will include tutorial update and a readable
>> API documentation). In the meantime, here are some hints about the changes:
>>
>>  - pyexiv2.Image is now called pyexiv2.ImageMetadata
>>  - the readMetadata() and writeMetadata() methods are now called read()
>> and write()
>>  - accessing tags using the [] operator on an ImageMetadata object will
>> return tag objects (where it previously returned only the value of the tag):
>> ExifTag, IptcTag, XmpTag
>>  - the tags store quite a lot of useful information about themselves,
>> including key, description, raw value (string), value (translated to a
>> pythonic type where applicable), ...
>>  - IptcTag objects always store a list of values even when the tag is not
>> repeatable (check the repeatable property)
>>
>> Instructions for testing:
>>
>> # Get the latest revision of the 0.2 branch
>> bzr branch lp:pyexiv2 && cd pyexiv2
>> # Compile it
>> scons
>> # Install it (to be run with administrative rights)
>> scons install
>>
>> When testing, make sure you have a backup of your data, especially if you
>> are modifying or writing metadata to files! Please report bugs at
>> https://bugs.launchpad.net/pyexiv2/+filebug. Any questions/doubts should
>> be directed to this mailing-list.
>>
>> My plans for the release include a windows installer. Since I'm not a
>> windows guy, I appreciate any help and hints in this field.
>>
>> Regards,
>>
>> Olivier
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~pyexiv2-developers<https://launchpad.net/%7Epyexiv2-developers>
>> Post to     : pyexiv2-developers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~pyexiv2-developers<https://launchpad.net/%7Epyexiv2-developers>
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>