is wxPython working with 2.6

wxPython Users
1

I have read a few posting that state 2.6 and wxPython are not happy with each
other even using the wxPython for 2.6. So is wxPython working correctly with
2.6?

···

--
John Fabiani

2

I'm not having any problems with it so far.

johnf wrote:

···

I have read a few posting that state 2.6 and wxPython are not happy with each
other even using the wxPython for 2.6. So is wxPython working correctly with
2.6?

3

I’m not having any problems either for several months now, and I started with code written for Python 2.5 and only switched because of the multiprocessing module. There aren’t really very many differences between 2.5 and 2.6, anyway. Some of our older code broke due to deprecations (“as” is now a reserved keyword, os.popen raises an error), but that was non-GUI stuff we wrote, not wxPython. I’m not using any bleeding-edge wxPython features either, however.

···

On Tue, Jan 6, 2009 at 2:32 PM, johnf jfabiani@yolo.com wrote:

I have read a few posting that state 2.6 and wxPython are not happy with each

other even using the wxPython for 2.6. So is wxPython working correctly with

2.6?

4

Thanks for the replies.

···

On Tuesday 06 January 2009 02:43:43 pm Nathaniel Echols wrote:

On Tue, Jan 6, 2009 at 2:32 PM, johnf <jfabiani@yolo.com> wrote:
> I have read a few posting that state 2.6 and wxPython are not happy with
> each
> other even using the wxPython for 2.6. So is wxPython working correctly
> with
> 2.6?

I'm not having any problems either for several months now, and I started
with code written for Python 2.5 and only switched because of the
multiprocessing module. There aren't really very many differences between
2.5 and 2.6, anyway. Some of our older code broke due to deprecations
("as" is now a reserved keyword, os.popen raises an error), but that was
non-GUI stuff we wrote, not wxPython. I'm not using any bleeding-edge
wxPython features either, however.

--
John Fabiani