PyCells: The Python SpreadSheet redux

In 2004 I saw a recipe about how to make a “spread­sheet” in python in 10 lines of code:

class SpreadSheet:
    _cells = {}
    tools = {}
    def __setitem__(self, key, formula):
        self._cells[key] = formula
    def getformula(self, key):
        return self._cells[key]
    def __getitem__(self, key ):
        return eval(self._cells[key],, self)

It’s shock­ing. And it work­s, too:

>>> from math import sin, pi
>>>, pi=pi, len=len)
>>> ss = SpreadSheet()
>>> ss['a1'] = '5'
>>> ss['a2'] = 'a1*6'
>>> ss['a3'] = 'a2*7'
>>> ss['a3']
>>> ss['b1'] = 'sin(pi/4)'
>>> ss['b1']
>>> ss.getformula('b1')

I was so awed, I wrote a PyQt ver­sion . Of course there is a catch in that code: it sucks if you are try­ing to write a spread­sheet with it.

Why? Be­cause it does­n’t store re­sult­s, but on­ly for­mu­las.

For ex­am­ple:


If you ask for the val­ue of A2, you get 4. If you set A1 to 7, what’s the val­ue of A2?

Well, it’s noth­ing yet, be­cause it’s on­ly cal­cu­lat­ed when you ask for it. But sup­pose you are try­ing to dis­play that sheet… you need to know A2’s val­ue changed when you set A1!

That’s cell de­pen­den­cies, and while that sim­ple code han­dles them in a way, it to­tal­ly sucks in an­oth­er.

So, I went ahead and cod­ed around it suc­cess­ful­ly. Of course the code was not so pret­ty any­more (although a large part of the ug­ly­ness is just for mak­ing it work with Python 2.3 and rel­a­tive cell­s).

Then yes­ter­day, while look­ing at the ex­cel for­mu­la pars­er mad­ness I saw a ref­er­ence to Py­Cells, a python port of Cells from CLOS.

Here is a blog com­ment­ing on Py­cells:

It basically takes the concept of a cell in a spreadsheet that get updated automatically to programming where there are a lot of internal data states that are dependent on one another in a chain, or a complex graph of dependencies. Like, the color of a button depends on whether you selected a radio button or not. Or, shut down the motor if the sensor reads above 100 degrees (example given in text).

Al­most ev­ery­one us­es that anal­o­gy… how­ev­er, no mat­ter how hard I looked, I could­n’t find any­one who had ac­tu­al­ly tried writ­ing a spread­sheet us­ing Py­Cell­s! Not even as an ex­am­ple!

So here it is:

import cells

class Cell(cells.Model):
    def value(self,prev):
        print "eval ",self.formula
        return eval(self.formula, {},
    def __init__(self, ss, *args, **kwargs):
        cells.Model.__init__(self, *args, **kwargs)

class ssDict:
        def __init__(self):

        def __getitem__(self,key):

        def __setitem__(self,key,v):
                if not

if __name__ == "__main__":
        ss['a1'] ='5'

        print "a1: ", ss['a1']
        print "a2: ", ss['a2']

        ss['a1'] = '7'
        print "a1: ", ss['a1']
        print "a2: ", ss['a2']

And here you can see it run­ning:

[ralsina@monty cells]$ python
a1:  eval  5
a2:  eval  2*a1
eval  7
eval  2*a1
a1:  7
a2:  14

See how when I set a1 to 7 I get “e­val 7” and “e­val 2*a1”? That’s be­cause it’s prop­a­gat­ing changes the right way. And that’s why this would work as a ba­sis for a spread­sheet.


It seems there is a bug with­er in Py­Cell­s, or in my ex­am­ple, or some­thing, be­cause it breaks pret­ty eas­i­ly, if the de­pen­den­cy chain is even two cell­s:

a1:  eval  5
a2:  eval  2*a1
a3:  eval  2*a2
eval  7
eval  2*a1
a1:  7
a2:  14
a3:  20

In this ex­am­ple, I am set­ting A3 to 2*A2, and when I up­date A1, A3 is not up­dat­ed. Fur­ther re­search is need­ed.


Please check the red­dit com­ments. They are very ed­u­ca­tion­al!


Comments powered by Disqus
Contents © 2000-2013 Roberto Alsina