Skip to main content

Installing python and friends on Windows (vista)

One way to go is to get the installer from Enthought [here]. This is the academic version, but their license agreement is not clear to me: it is not clear that even as a researcher working on public money in a university doing research I publish in publicly accessible journals and make available on my website, I can use this distribution. What you pay for is the convenience of having a lot of open source python related software bundled together. You also get a lot of packages you may not be using.

For me, the old fashioned hunter gatherer lifestyle leads me to the following course of action:
  1. Download and install python using the installer [python.org]
  2. Download and install setup tools [python.org, scroll to the bottom]
  3. Run command prompt as admin to use easy_install [guide here]
  4. Install ipython
    easy_install http://ipython.scipy.org/dist/ipython-0.8.2-py2.5.egg
    easy_install http://ipython.scipy.org/dist/pyreadline-1.5.dev_r2876-py2.5.egg
    [or whatever versions you want from that page]
  5. Install numpy
    The egg is through sourceforge, which doesn't have direct access, so download it to a directory and then use the egg from there
    easy_install "D:\Documents\My Downloads\numpy-1.0.4-py2.5-win32.egg"
  6. Install scipy
    Download the egg from sourceforge, and then easy_install:
    easy_install "D:\Documents\My Downloads\scipy-0.6.0-py2.5-win32.egg"
  7. Install matplotlib
    The egg is through sourceforge, which doesn't have direct access, so download it to a directory and then use the egg from there
    easy_install "D:\Documents\My Downloads\matplotlib-0.91.2.win32-py2.5.egg"
These steps take care of everything including 2D plots that are exportable to svg, but what about 3D plots? This gets more tricky.
Labels:

Comments

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