Comment 1 for bug 188395

I couldn't actually replicate this behaviour, so I've switched the code back - if you do get it again, do the following:

* In the first line of the method, put "import pdb ; pdb.set_trace()"

* When the trace starts, run the following commands:

  - print creep, id(creep)
  - print self.creeps, [ id(c) for c in self.creeps ]
  - print creep in self.creeps

Chuck the output of those onto this ticket, we'll have a closer look. If you haven't used pdb before, it's a worthwhile tool to get used to - helps a lot ;) Just never check a pdb statement in, it confuses the end users...