FIFE forums

Please login or register.

Login with username, password and session length
Advanced search  

News:

FIFE 0.4.0 has been released on 15th of January, 2017!

Author Topic: Python 2.6  (Read 2160 times)

readlock

  • Newbie
  • Posts: 4
    • View Profile
Python 2.6
« on: May 28, 2009, 12:35:51 pm »

Is this ticket still active? For Windows maybe? I have successfully compiled FIFE with Stackless instead of generic Python.

Rio and PARPG work. Some FIFE tests don't work, I'll provide more info if needed.

Arch Linux on Intel 64.

uname -a: Linux obfuscate 2.6.29-ARCH #1 SMP PREEMPT XXX x86_64 Intel(R) Core(TM)2 Duo CPU T5670 @ 1.80GHz GenuineIntel? GNU/Linux

python sys.version: '2.6.1 Stackless 3.1b3 060516 (python-2.6.1:67756, May 18 2009, 18:54:01) \n[GCC 4.3.3]'

FIFE: svn 2837 PARPG: svn 75
Logged

CheeseSucker

  • Developer
  • Newbie
  • *
  • Posts: 26
  • FIFE programmer
    • View Profile
Re: Python 2.6
« Reply #1 on: May 28, 2009, 12:42:11 pm »

Fixed in http://mirror1.cvsdude.com/trac/fife/engine/changeset/2688: "Buildscripts have been modified to work with different python versions. This applys only to linux/freebsd/darwin. For windows the only supported python version remains 2.5.x. On linux/freebsd/darwin 2.5 and 2.6 should work."

However, I do suspect 2.6 will work on windows. (can anyone confirm this?)
Logged

readlock

  • Newbie
  • Posts: 4
    • View Profile
Re: Python 2.6
« Reply #2 on: May 28, 2009, 12:59:44 pm »

Maybe build/win32-config-dist.py should have some path-manipulation, too, like http://pastebin.com/m3e0463cb ?
« Last Edit: June 05, 2009, 04:20:17 am by readlock »
Logged

mvBarracuda

  • Administrator
  • Sr. Member
  • *
  • Posts: 411
    • View Profile
Re: Python 2.6
« Reply #3 on: June 05, 2009, 07:04:58 am »

On win32 the only realistic option to build FIFE from source is the win32 compile SDK. As it ships with Python 2.5, we shouldn't give the impression that other Python versions are supported in theory, at least not without a lot of extra work for the person who compiles it. Therefore I would propose to leave the win32-config-dist.py as it is and leave any kind of manipulation to the person who might try to build not with the compile SDK.
Logged