Next | Query returned 23 messages, browsing 21 to 30 | previous

History of commit frequency

CVS Commit History:


   2019-11-13 21:56:09 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
Log message:
py-tables: updated to 3.6.1

Changes from 3.6.0 to 3.6.1
Maintenance release to fix packaging issues. No new features or bugfixes.

Changes from 3.5.3 to 3.6.0
PyTables 3.6 no longer supports Python 2.7.

Improvements
- Full python 3.8 support.
- On Windows PyTables wheels on PyPI are linked to `pytables_hdf5.dll` instead of
 `hdf5.dll` to prevent collisions with other packages/wheels that also vendor \ 
`hdf5.dll`.
 This should prevent problems that arise when a different version of a dll is \ 
imported
 that the version to which the program was linked to. This problem is known as \ 
"DLL Hell".
 With the renaming of the HDF5 DLL to `pytables_hdf5.dll` these problems should \ 
be solved.

Bugfixes
- Bugfix for HDF5 files/types with padding. For details see :issue:`734`.
- More fixes for python 3.8 compatibility: Replace deprecated time.clock
  with time.perf_counter
- Improvements in tests as well as clean up from dropping Python 2.7 support.
   2019-06-14 17:13:35 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-tables: updated to 3.5.2

Changes from 3.5.1 to 3.5.2
- Fixed compatibility with python 3.8: Fixed `Dictonary keys changed during
  iteration` RuntimeError while moving/renameing a node.
  Thanks to Christoph Gohlke for reporting and Miro Hroncok for help with
  building PyTables for python 3.8alpha (cython compatibility).
- Fixed a bug in offset calculations producing floats instead of ints
  affecting python 3.
   2019-03-20 17:08:06 by Adam Ciarcinski | Files touched by this commit (4) | Package updated
Log message:
py-tables: updated to 3.5.1

Changes from 3.5.0 to 3.5.1
- Maintenance release to fix how PyPi repo is handling wheel versions.

Changes from 3.4.4 to 3.5.0
Improvements
- When copying data from native HDF5 files with padding in compound types,
  the padding is not removed now by default.  This allows for better
  compatibility with existing HDF5 applications that expect the padding
  to stay there.
  Also, when the description is a NumPy struct array with padding, this
  is honored now.  The previous behaviour (i.e. getting rid of paddings) can
  be replicated by passing the new allow_padding parameter when opening
  a file.  For some examples, see the new examples/tables-with-padding.py
  and examples/attrs-with-padding.py.
- Added a new flag --dont-allow-padding in ptrepack utility so as to
  replicate the previous behaviour of removing padding during file copies.
  The default is to honor the original padding in copies.
- Improve compatibility with numpy 1.16.
- Improve detection of the LZO2 library at build time.
- Suppress several warnings.
- Add AVX2 support for Windows.

Next | Query returned 23 messages, browsing 21 to 30 | previous