-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Emma Strubell wrote:
There must be a faster python pickler out there, though, any
recommendations?
Right off the bat, you might try cPickle. It should work identically,
just faster. Also you can try importing psyco, if it's present it will
try
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry,
I lost my notes from when I last looked these over several months ago,
and only just found them again. I haven't copied this to [EMAIL PROTECTED], so
let me know if I should do that. I just had a quick couple of things I
was thinking
Jim,
I opened bug 158632, so that's worth looking at. It also points to a
post on the forums about the problem. I can't add much to the
discussion myself, just that it affected two of my machines differently
which I found rather odd (one has difficulty with all versions of mpc,
the other
Ok,
Well, what if instead we were to try and treat the overlay trees as
exactly that, overlays. So the moves were used from the lowest layer
(ie the main tree) unless a higher up layer overrode them, could that
work? It would mean effectively that the overlay moves were global, but
I guess
Yeah,
Sorry about the double posting, patrick told me about a gmail feature
that means you never see your own posts...
I agree that the updates should only affect that individual tree.
Whilst I can imagine cases where a move in the main tree should affect
overlay trees (such as
