[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: HDF5 1.10 transition?



Il 31/10/2016 01:32, Antonio Valentino ha scritto:
> Hi Gilles,
> 
> Il 30/10/2016 20:57, Gilles Filippini ha scritto:
>> Antonio Valentino a écrit le 30/10/2016 à 18:16 :
>>> Hi Gilles,
>>>
>>> Il 29/10/2016 17:17, Gilles Filippini ha scritto:
>>>> On 2016-10-25 09:42, Jerome Kieffer wrote:
>>>>> On Tue, 25 Oct 2016 08:13:43 +0100
>>>>> Ghislain Vaillant <ghisvail@gmail.com> wrote:
>>>>>
>>>>>>

[CUT]

>>>> Unfortunaly it is far from achieved and the dedicated 'pt4' branch of
>>>> the pytables repo is stalled since late august. Thus the 'pytables overs
>>>> h5py' option seems dead for Stretch release.
>>>
>>> Yes I can confirm that pt4 is not an option for Stretch.
>>> The PyTable project is currently moving very slowly due to lack of time
>>> of the maintainers (including me).
>>>
>>>> This left us with the 'embed hdf5 1.8.16 into the pytable package' option.
>>>>
>>>> Antonio, any thought about this?
>>>
>>> In theory pytables should be able to work with HDF5 1.10 using the old
>>> 1.8 API.
>>> Unfortunately it seems that there is some compatibility issue (see also
>>> [1]) that none of the PyTables maintainers had the time to fix.
>>> IMHO a patch for PyTables v3.3 to fix compatibility with HDF5 1.10 would
>>> be a better option if someone has some time to dedicate to it.
>>
>> The HDF5 1.10 package in experimental was built with
>> "--with-default-api-version=v18". But there is one major difference with
>> 1.8.x releases: hid_t is now 64 bit integer instead of standard int.
>>
>> I gave a try patching pytables v3.3 in some obvious places, with no
>> success at all. Any help on this side would be greatly appreciated.
> 
> OK, I think I have fixed all main issues with HDF5 1.10.
> I'm currently testing my patches and I will open a PR upstream ASAP (in
> an hour I hope).

the fix is available at

https://github.com/PyTables/PyTables/pull/582


cheers

-- 
Antonio Valentino

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: