timonecomcastnet tim peters neale pickett hacked something turn wordinfo tuple pickling thats wordinfo__getstate__ turn tuple back wordinfo right unpickling likewise wordinfo__setstate__ without hack database 21549056 bytes 9945088 bytes thats 50 savings bad optimization im sure youre suspect youre storing individual wordinfo pickles administrative pickle bloat due doesnt happen pickle entire classifier instance directly question would painful ditch wordinfo favor straight tuple list youd rather although making tuple nice sideeffect forcing play nice dbdict class hope sort optimization isnt far distant goal project even though readmetxt says diff attached im comfortable checking think healthy youre uncomfortable checking things xxx kludge kludge kludge comments since dont really like works id rather get rid wordinfo guess proves point im interested optimizing anything yet get many benefits ease working utterly vanilla python instance objects lots code picks apart display analysis purposes people tried code yet still many questions see eg jeremys writeup disappointing firsttime experiences today lets keep easy possible modify youre desparate save memory write subclass people free vote directions course fri 06 sep 2002 200656 0400 spambayes ditching wordinfo