Python 2.6 and SPSS integration

[catsclaw]

Hi all --

   I'm trying to move my development from Python 2.5 to Python 2.6 in
anticipation of moving to Python 3.0, but the SPSS Python integration
module doesn't support 2.6.
   Are there any plans to release a new version of the Integration
Module for Python 2.6?  What about Python 3.0?

-- Chris

=====================
To manage your subscription to SPSSX-L, send a message to
[hidden email] (not to SPSSX-L), with no body text except the
command. To leave the list, send the command
SIGNOFF SPSSX-L
For a list of commands to manage subscriptions, send the command
INFO REFCARD

[Peck, Jon]

You will have to stick with 2.5 with SPSS version 17.  Of course we expect to move to newer versions with new releases, but 3.0 is brand new, and it is not ready for production use IMO.  Besides the language engine itself, many of the libraries and extensions have not yet been converted.  There were significant changes to the C interfaces, so they have to be reworked.

2.6 is an important transitional release.  It is possible that you could build a 2.6-compatible version of the plug-in using the SDK on Developer Central.  We had hoped to move to 2.6 with version 17, but it was not ready in time.

Regards,
Jon Peck
-----Original Message-----
From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of Chris Bergstresser
Sent: Wednesday, December 17, 2008 4:32 PM
To: [hidden email]
Subject: [SPSSX-L] Python 2.6 and SPSS integration

Hi all --

   I'm trying to move my development from Python 2.5 to Python 2.6 in
anticipation of moving to Python 3.0, but the SPSS Python integration
module doesn't support 2.6.
   Are there any plans to release a new version of the Integration
Module for Python 2.6?  What about Python 3.0?

-- Chris

=====================
To manage your subscription to SPSSX-L, send a message to
[hidden email] (not to SPSSX-L), with no body text except the
command. To leave the list, send the command
SIGNOFF SPSSX-L
For a list of commands to manage subscriptions, send the command
INFO REFCARD

=====================
To manage your subscription to SPSSX-L, send a message to
[hidden email] (not to SPSSX-L), with no body text except the
command. To leave the list, send the command
SIGNOFF SPSSX-L
For a list of commands to manage subscriptions, send the command
INFO REFCARD

[catsclaw]

On Wed, Dec 17, 2008 at 5:59 PM, Peck, Jon <[hidden email]> wrote:
> Of course we expect to move to newer versions with new releases, but 3.0
> is brand new, and it is not ready for production use IMO.

   I don't disagree, but there's a lot of language features which have
been backported to 2.6.  Writing code to Python 2.6 is going to make
it easier to switch when the time comes, and that combined with the
speed improvements in parts of the Python engine makes it a compelling
option for us.

> It is possible that you could build a 2.6-compatible version of the plug-in
> using the SDK on Developer Central.  We had hoped to move to 2.6 with
> version 17, but it was not ready in time.

   Alas, getting the compiler environment set up to recompile the code
is a bit daunting.  It seemed like it should just be a matter of
compiling against the 2.6 Python dll rather than the 2.5 dll.
Obviously, from a corporate standpoint it's not that simple (the
install needs to be rewritten to take that into account; the files
need to be packaged, hosted, and published; etc ...) but the actual
technical work seemed almost trivial.  Or potentially so, anyway.

-- Chris

=====================
To manage your subscription to SPSSX-L, send a message to
[hidden email] (not to SPSSX-L), with no body text except the
command. To leave the list, send the command
SIGNOFF SPSSX-L
For a list of commands to manage subscriptions, send the command
INFO REFCARD