If you are a Wesnoth packager for the 1.5.x series, I'm asking you to please consider packaging Python 2.5.x, versus 2.4.x, in your next build. This is NOT a requirement and is only a request.
The benefits of migrating to Python 2.5 (2.5.2 as of this writing) are simple. Python 2.5 has both new language features and new optimizations. Given that AIs tend to be CPU bound, performance boosts are certainly appreciated. Beyond the performance gains, I am creating a new, higher level module called Wesnoth AI Library, or wail for short, which sits on top of the existing wesnoth module. This module makes use of new 2.5 language features. In the event Python 2.5 is not packaged, existing AIs will continue to run and compatibility is ensured. As I said before, this is not a requirement. However, newer AIs which make use of the wail module, once released, will not be compatible with any package built against Python 2.4. As such, it is to the advantage of the Wesnoth Python AI community to include Python 2.5 where possible. Thus far the developers and packagers I've spoken with have been very receptive. Thanks to everyone for their support in this initiative. If you have questions, comments, or concerns, please feel free to email me or the list. Cheers, Greg Oracle BlindOracle _______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
