Bug 24533 - Update python-h5py to 2.9.0
Summary: Update python-h5py to 2.9.0
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Python Stack Maintainers
QA Contact:
URL: https://madb.mageia.org/package/show/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-19 12:17 CET by kunda 1
Modified: 2021-07-04 08:38 CEST (History)
3 users (show)

See Also:
Source RPM: python-h5py-2.8.0-4.mga7
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description kunda 1 2019-03-19 12:17:00 CET 
Latest stable is 2.9.0 
https://github.com/h5py/h5py/releases/tag/2.9.0


```
This is the first release of the h5py 2.9 series

This release support Python 2.7 and Python 3.4-3.7

Features:
 - Convenient high-level API for creating virtual datasets
 - Construct an h5py.File from a python file-like object
 - File now takes parameters for controlling the chunk cache
 - Option to preserve insertion order of attribute and group entries
 - Can now create datasets backed by external non-HDF5 files
 - List and tuples of rriunicode strings can be stored as HDF5 attributes

Bug fixes:
 - Fix reading/writing of float128 data
 - Fix converting data to float16 when creating a dataset

Support for old Python
 - Drops support for Python 3.3
 - Drops support for Python 2.6
```
Comment 1 Marja Van Waes 2019-03-19 13:54:56 CET 
Assigning to the Python stack maintainers, CC'ing the registered maintainer.

Summary: Update h5py to 2.9.0 => Update python-h5py to 2.9.0
Source RPM: https://madb.mageia.org/rpm/show/source/1/application/0/release/cauldron/name/python-h5py-2.8.0-4.mga7.src.rpm/arch/i586/t_media/3 => python-h5py-2.8.0-4.mga7
CC: (none) => joequant, marja11
Assignee: bugsquad => python

Comment 2 papoteur 2021-07-04 08:38:02 CEST 
Mgeia 8 has now 2.9.0-5.mga8
Thus closing

Status: NEW => RESOLVED
CC: (none) => yves.brungard_mageia
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.