{ stdenv, lib, fetchPypi, python, buildPythonPackage , cython, bzip2, lzo, numpy, numexpr, hdf5, six, c-blosc, mock }: with stdenv.lib; buildPythonPackage rec { version = "3.5.2"; pname = "tables"; src = fetchPypi { inherit pname version; sha256 = "1hikrki0hx94ass31pn0jyz9iy0zhnkjacfk86m21cxsc8if685j"; }; buildInputs = [ hdf5 cython bzip2 lzo c-blosc ]; propagatedBuildInputs = [ numpy numexpr six mock ]; # The setup script complains about missing run-paths, but they are # actually set. setupPyBuildFlags = [ "--hdf5=${getDev hdf5}" "--lzo=${getDev lzo}" "--bzip2=${getDev bzip2}" "--blosc=${getDev c-blosc}" ]; # Run the test suite. # It requires the build path to be in the python search path. # These tests take quite some time. # If the hdf5 library is built with zlib then there is only one # test-failure. That is the same failure as described in the following # github issue: # https://github.com/PyTables/PyTables/issues/269 checkPhase = '' ${python.interpreter} <