Mark Wedel wrote: > Todd Mitchell wrote: > >> Well 2.1 was what I always am pushing because of Debian. If we stop >> supporting python 2.1 we stop python support in CF for woody - this >> impacts CF servers for the mainstream debian crowd. Although many folks >> use testing or unstable for desktop (including me), I think many folks >> might still use woody for public servers (including me). Sarge uses >> Python 2.3 however so hopefully one day soon this will be resolved. > > > Well, it seems there are really two choices: > > a) Support python 2.1, but then have things that need 64 bit values be > broken (exp, money, etc). > > b) Support only version 2.2 and newer, which may lose support of older > platforms for the python plugin (rest of crossfire would still work > fine). > > I think 'b' is the way to go - no reason to try to support older > technology software that may not work really well. Also, if it is > important for those still using that older software, they could always > install a newer version of python someplace else just for crossfire to > use. > > The real problem, of course, is precompiled packages - either you do > the precompiled package with python support, which may have issues > with debian, or you don't, which means people running the latest > version have issues (or you two distributions). > > But I don't even know if anyone is doing precompiled debian packages > anyways, so may not be an issue. > I'd go along with this - the deb version of CF server in Woody is not even close to current. I just mentioned it as something to keep in mind - maybe some sort of howto or notification on how to build Crossfire with a alternate python path is in order. (I believe it is configure -- pythonsomething=<path>). Also I would in this case suggest we jump over 2.2 and make 2.3 (or even 2.4?) the new 'test target' for crossfire python. This will give us a longer period of stability again and there are some nice things in there we can benefit from (like universal line ending and dictionary iteration in 2.3). Also I believe that real-time is moving from redhat to debian so this issue may be more salient as this goes on. _______________________________________________ crossfire-devel mailing list crossfire-devel at lists.real-time.com https://mailman.real-time.com/mailman/listinfo/crossfire-devel