=============================
Announcing PyTables 3.0.0rc2
=============================
We are happy to announce PyTables 3.0.0rc2.
PyTables 3.0.0rc2 comes after about 5 years from the last major release
(2.0) and 7 months since the last stable release (2.4.0).
This is new major release and an important milestone for the PyTables
project since it provides the long waited support for Python 3.x, which
has been around for 4 years.
Almost all of the core numeric/scientific packages for Python already
support Python 3 so we are very happy that now also PyTables can provide
this important feature.
Changes from 3.0rc1 to 3.0rc2
=============================
- The internal Blosc_ library has been upgraded to version 1.2.3.
- All methods of the :class:`Table` class that take *start*, *stop* and
*step* parameters (including :meth:`Table.read`, :meth:`Table.where`,
:meth:`Table.iterrows`, etc) have been redesigned to have a consistent
behaviour. The meaning of the *start*, *stop* and *step* and their
default values now always work exactly like in the standard
:class:`slice` objects.
Closes :issue:`44` and :issue:`255`.
- The :meth:`iterrows` method of :class:`*Array` and :class:`Table` as
well as the :meth:`Table.itersorted` now behave like functions in the
standard :mod:`itertools` module.
If the *start* parameter is provided and *stop* is None then the
array/table is iterated from *start* to the last line.
In PyTables < 3.0 only one element was returned.
- Fixed :issue:`119`, :issue:`230` and :issue:`232`, where an index on
:class:`Time64Col` (only, :class:`Time32Col` was ok) hides the data on
selection from a Tables. Thanks to Jeff Reback.
- Fixed an issue of the :meth:`Table.itersorted` with reverse iteration
(closes :issue:`252` and :issue:`253`).
--
Antonio Valentino
|
