Changelog History
-
v1.2.1 Changes
April 13, 2018โก๏ธ C-Blosc internal sources updated to 1.14.3. This basically means that
internal Zstd sources are bumped to 1.3.4, which may lead to noticeable
๐ improved speeds (specially for low compression ratios).np.datetime64
and other scalar objects that have__getitem__ ()
are now
supported in_eval_blocks()
. PR #377. Thanks to apalepu23.โก๏ธ Vendored cpuinfo.py updated to 4.0.0 (ARM aarch64 is recognized now).
๐ Allow setup.py to work even if not on Intel or ARM or PPC archs are found.
-
v1.2.0 Changes
March 23, 2018๐ Support for Python <= 2.6 or Python <= 3.4 has been deprecated.
โก๏ธ C-Blosc internal sources updated to 1.14.2. Using a C-Blosc library > 1.14 is important for forward compatibility. For more info see: http://blosc.org/posts/new-forward-compat-policy/
-
v1.1.2
February 02, 2017 -
v1.1.1 Changes
February 01, 2017๐ Changes from 1.1.0 to 1.1.1
๐ Allow to delete all the columns in a ctable. Fixes #306.
๐ Double-check the value of a column that is being overwritten. Fixes
#307.๐ Use
pkg_resources.parse_version()
to test for version of packages.
๐ Fixes #322.Now all the columns in a ctable are enforced to be a carray instance
in order to simplify the internal logic for handling columns.Now, the cparams are preserved during column replacement, e.g.:
ct['f0'] = x + 1
will continue to use the same cparams than the original column.
โก๏ธ C-Blosc updated to 1.11.2.
โ Added a new
defaults_ctx
context so that users can select defaults
easily without changing global behaviour. For example::0๏ธโฃ with bcolz.defaults_ctx(vm="python", cparams=bcolz.cparams(clevel=0)):
cout = bcolz.eval("(x + 1) < 0")๐ Fixed a crash occurring in
ctable.todataframe()
when bothcolumns
andorient='columns'
were specified. PR #311. Thanks to Peter
Quackenbush. -
v1.1.0
June 10, 2016 -
v1.0.0
April 07, 2016 -
v1.0.0.rc2
March 31, 2016 -
v1.0.0.rc1
March 08, 2016 -
v0.12.1
November 30, 2015 -
v0.12.0
November 16, 2015