[CF-Devel] Python questions

[crossfire-devel at archives.real-time.com]

Well by 'test target' I just meant the generally agreed on version that 
python scripts should be tested out on for inclusion to CVS, not a 
required version of Python for the server. Local and in-house scripts 
naturally don't need to worry about this and should be able to use 
whatever version of python they want/require.   However I think it's a 
good idea for the 'official' scripts to be tested against an agreed on 
version.  As an example I currently test against 2.1 for crossfire and 
can't say that the player log or slotmachines would work in 2.0 or 1.5 
or whatever but they will very likely work with 2.2 or 2.3, however when 
python scripts submitted for Guild system were tested on 2.3 there were 
cases of them not working on metalforge.  Basically I was just looking 
for an agreement something like the 'rules' we use for maps.  This will 
make it easier when people have problems as well - you have a version 
number to give them.  I would rather test scripts against 2.3 than 2.2 
as it is more current (so longer shelf-life)  has some big improvements 
and I think more likely to be installed on someone's system than 2.2.
I also didn't mean to imply that a check needs to be done on the server 
for a specific python version requirement, I just meant putting a nice 
notice in the INSTALL doc on how to use the configure script to build 
against a specific installation of python if your default system python 
does not work or if you want to keep it seperate.

Mark Wedel wrote:

>
     
       I'd be inclined not to make a specific version a requirement until 
     
     >
     
      features that require that version are put in place.
     
     >
     
     
     >
     
       It shouldn't be hard to just put in basic version checking - to some 
     
     >
     
      extent, the config program already does this just by searching for 
     
     >
     
      python.  Perhaps life could be made easier by putting something like 
     
     >
     
      'MIN_PYTHON_VERSION' as a define or the like to make it easier to update.
     
     >
     
     
     >
     
       The real problem of requiring later version when it isn't needed is 
     
     >
     
      that someone doesn't have that later version and figures out how to 
     
     >
     
      fool the config scripts or whatever to use the older version, and then 
     
     >
     
      poses the question 'why do you require version XYZ if you don't need 
     
     >
     
      it', of which there isn't a great answer.
     
     >
     
     
     >
     
       In terms of requiring 2.4, that seems quite bleeding edge - I have a 
     
     >
     
      feeling if that is required, 90% of the people would need to download 
     
     >
     
      it special (won't be included by default in what they are running).  
     
     >
     
      So there is a fine line between requiring what is needed matched 
     
     >
     
      against what people are actually using.
     
     >
     
     
     
_______________________________________________
crossfire-devel mailing list
     
     crossfire-devel at lists.real-time.com
     
     
     https://mailman.real-time.com/mailman/listinfo/crossfire-devel