[PEAK] Strange dispatch problem after cvs up

[Phillip J. Eby]

At 10:10 AM 4/24/05 -0700, Dave Peticolas wrote:
>On Sun, 2005-04-24 at 03:33 -0400, Phillip J. Eby wrote:
> > Anyway, it's fixed now, but we should probably make a move to Python 
> 2.4 in
> > the near future in order to get away from this problem.
>
>Any chance that 2.3 compatibility could be retained to a 1.0 release?

Sure.  You meant 1.0 alpha, right?  ;)

Interestingly enough, Google is still on Python 2.2, so at least you can 
say you're more advanced than Google.  :)

Seriously, though, I'm not sure.  Python 2.4 has an additional advantage in 
having fast set types, although I'm not sure I'm not going to wind up 
writing my own bitset and run-length-encoded integer sets in C just to get 
the best possible memory/speed for some operations.  OTOH, maybe those'll 
be 1.1 enhancements.  I should probably just get to work on docs after the 
cleanup pass is done and get on with it.

In short, I'll try to stick with 2.3 compatibility for a while, but working 
with 2.4 regularly for OSAF stuff is really starting to spoil me.  :)