Diffrences: Python 2.3 and Python 2.4

[Extremist]

Hi there,

I have an application written in Python 2.3, wxPython 2.4 , C++, OpenGL
OS: Fedora Core 3

Now I need to upgrade it using Python 2.4 and wxPython 2.6 OS: Fedora Core 6
There was a few minor faults and it was easy to fix
But now I get this Segmentation fault error message

What is the diffrences between Python 2.3 and Python 2.4?
What is the diffrences between wxPython 2.4 and wxPython 2.6?

[bartonc]

Hi there,

I have an application written in Python 2.3, wxPython 2.4 , C++, OpenGL
OS: Fedora Core 3

Now I need to upgrade it using Python 2.4 and wxPython 2.6 OS: Fedora Core 6
There was a few minor faults and it was easy to fix
But now I get this Segmentation fault error message

What is the diffrences between Python 2.3 and Python 2.4?
What is the diffrences between wxPython 2.4 and wxPython 2.6?

The big problems seem to come when attempting to import modules that were compiled with earlier versions of the core include and header files into a newer version of python. On Widows, we get a very clear message that say something like "that was compiled with an earlier version of python". I've also read that compiled modules should be built with THE SAME compiler as python was built with, but, again, this issue is seldom seen on Windows because the production version of python is built with VC++. So if you have source code you can compile troublesome modules with current include and header files. If not look for current binaries (I have this problem with python-MySQLd).
As for wx, I didn't start using it until V2.6 and skipped the part of the release notes that talked about backward compatability. I do know that there are some issues, however. Of course, wx is now in version 2.8 as of December, 2006.

[Extremist]

The big problems seem to come when attempting to import modules that were compiled with earlier versions of the core include and header files into a newer version of python. On Widows, we get a very clear message that say something like "that was compiled with an earlier version of python". I've also read that compiled modules should be built with THE SAME compiler as python was built with, but, again, this issue is seldom seen on Windows because the production version of python is built with VC++. So if you have source code you can compile troublesome modules with current include and header files. If not look for current binaries (I have this problem with python-MySQLd).
As for wx, I didn't start using it until V2.6 and skipped the part of the release notes that talked about backward compatability. I do know that there are some issues, however. Of course, wx is now in version 2.8 as of December, 2006.

I am going to check it out. But wxPython is only a GUI toolkit. Off course I am used to working on Windows from home as well. So far I havent test this program's compatibility on windows, thank you for your input

[bartonc]

I am going to check it out. But wxPython is only a GUI toolkit. Off course I am used to working on Windows from home as well. So far I havent test this program's compatibility on windows, thank you for your input

You are welcome for the input. I have gotten to know wxPython quite well over the past 6 months (the most common widgets and all the methods of EVT_* class objects), so if you have questions there, I can probably guide you.

[Extremist]

You are welcome for the input. I have gotten to know wxPython quite well over the past 6 months (the most common widgets and all the methods of EVT_* class objects), so if you have questions there, I can probably guide you.

Well, Thank you for the offer.
I myself have gotton to know wxPython quite well.
My problem is that I know wxPython 2.6 > better than I know wxPython 2.4
And the same with Python 2.4 > better than Python 2.3

[bartonc]

Well, Thank you for the offer.
I myself have gotton to know wxPython quite well.
My problem is that I know wxPython 2.6 > better than I know wxPython 2.4
And the same with Python 2.4 > better than Python 2.3

Sounds like our skill sets may be on about the same level. I've never even tried to to stay 2.3 compatible. It seems like most significant changes took place in 2.2 and maybe now with 2.5 some new syntax has evolved, but I haven't really checked it out too much.

[Extremist]

Sounds like our skill sets may be on about the same level. I've never even tried to to stay 2.3 compatible. It seems like most significant changes took place in 2.2 and maybe now with 2.5 some new syntax has evolved, but I haven't really checked it out too much.

Exactly, I have the same problem.
I am forced though to still use Python 2.3 and Python 2.4
I get an error with SetStringSelect ion.
[ERROR] wxPython.wxc.wx PyAssertionErro r
C++ assertion "wxAssertFailur e" failed in ../src/common/lboxcmn.cpp(81) : invalid string in SetStringSelect ion [/ERROR]

 self.R.SetStringSelection(rol 

)

[bartonc]

Exactly, I have the same problem.
I am forced though to still use Python 2.3 and Python 2.4
I get an error with SetStringSelect ion.
[ERROR] wxPython.wxc.wx PyAssertionErro r
C++ assertion "wxAssertFailur e" failed in ../src/common/lboxcmn.cpp(81) : invalid string in SetStringSelect ion [/ERROR]

 self.R.SetStringSelection(rol 

)

This does not look like a python error (or version problem). Your wxPython version may be out of sink with wxWidgets installed. Post enough code to run and I'll try to run it to see if I get the same error. I am currnetly using Py2.4.4 because of current MySQL support.

[Extremist]

This does not look like a python error (or version problem). Your wxPython version may be out of sink with wxWidgets installed. Post enough code to run and I'll try to run it to see if I get the same error. I am currnetly using Py2.4.4 because of current MySQL support.

What I haven't mensioned is that the application I am working on is very big, 1 Gb of code.
Keeping that in mind, you can understand that there is a lot of imports depending on each other, sending you enough code, isn't quite possible
But the good news is that I think I found my problem. A wxWidget problem.
Thank you so much for your help

[bartonc]

What I haven't mensioned is that the application I am working on is very big, 1 Gb of code.
Keeping that in mind, you can understand that there is a lot of imports depending on each other, sending you enough code, isn't quite possible
But the good news is that I think I found my problem. A wxWidget problem.
Thank you so much for your help

OK, here's the plan: Make a simpleApp with enough code to produce the error on your machine. Then start a new discussion and post your simpleApp there and I'll run it. We should be targeting the wx installation since that is what the error looks like to me.