Skip to main content

Mac OS X install pytables and h5py

  1. Install tables - need NumPy version 1.6
  2. Get NumPy from sourceforge and install - need Python 2.7
  3. Install python 2.7 on Lion, open new terminal (or refresh path)
  4. curl http://python-distribute.org/distribute_setup.py | python
  5. curl https://raw.github.com/pypa/pip/master/contrib/get-pip.py | python
  6. sudo pip install ipython
  7. sudo pip install tables
  8. need numexpr > 1.4.1, 
  9. Download anc ompile numexpr -> wants to compile using gcc-4.2
  10. sudo ln -s gcc gcc-4.2
  11. sudo pip install cython
  12. Get HDf5 from http://www.hdfgroup.org/ftp/HDF5/current/bin/mac-intel-x86_64/hdf5-1.8.8-mac-intel-x86_64-shared.tar.gz
  13. /configure and compile
  14. Copy the hdf5 folder whereever you want
  15. python setup.py build --hdf5=/path/to/hdf5 (from the unzipped source of h5py)
  16. sudo python setup.py install --hdf5=/usr/local/hdf5/ (in the unzipped dir of pytables)
In contrast, to get h5py working on Ubuntu:

sudo apt-get install libhdf5-serial-dev
 
sudo easy_install h5py
Labels:

Comments

  1. NathanMarch 27, 2013 at 1:12 AM

    Very useful. Suprisingly few links found in google for this issue.

    Thanks a lot.

    ReplyDelete

Post a Comment

Popular posts from this blog

A note on Python's __exit__() and errors

Python's context managers are a very neat way of handling code that needs a teardown once you are done. Python objects have do have a destructor method ( __del__ ) called right before the last instance of the object is about to be destroyed. You can do a teardown there. However there is a lot of fine print to the __del__ method. A cleaner way of doing tear-downs is through Python's context manager , manifested as the with keyword. class CrushMe: def __init__(self): self.f = open('test.txt', 'w') def foo(self, a, b): self.f.write(str(a - b)) def __enter__(self): return self def __exit__(self, exc_type, exc_val, exc_tb): self.f.close() return True with CrushMe() as c: c.foo(2, 3) One thing that is important, and that got me just now, is error handling. I made the mistake of ignoring all those 'junk' arguments ( exc_type, exc_val, exc_tb ). I just skimmed the docs and what popped out is that you need to return True or...
Post a Comment
Read more

Store numpy arrays in sqlite

Use numpy.getbuffer (or sqlite3.Binary ) in combination with numpy.frombuffer to lug numpy data in and out of the sqlite3 database: import sqlite3, numpy r1d = numpy.random.randn(10) con = sqlite3.connect(':memory:') con.execute("CREATE TABLE eye(id INTEGER PRIMARY KEY, desc TEXT, data BLOB)") con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", sqlite3.Binary(r1d))) con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", numpy.getbuffer(r1d))) res = con.execute("SELECT * FROM eye").fetchall() con.close() #res -> #[(1, u'1d', <read-write buffer ptr 0x10371b220, size 80 at 0x10371b1e0>), # (2, u'1d', <read-write buffer ptr 0x10371b190, size 80 at 0x10371b150>)] print r1d - numpy.frombuffer(res[0][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] print r1d - numpy.frombuffer(res[1][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] Note that for work where data ty...
Post a Comment
Read more