The 2.8.8.1 release of wxPython is now available for download at http://wxpython.org/download.php. This is a minor bugfix release with
several fixes for problems discovered in the 2.8.8.0 release.
Source code is available, as well as binaries for Python 2.3, 2.4 and
2.5, for Windows and Mac, as well some packages for various Linux
distributions. A summary of changes is listed below and also at http://wxpython.org/recentchanges.php.
What is wxPython?
-----------------
wxPython is a GUI toolkit for the Python programming language. It
allows Python programmers to create programs with a robust, highly
functional graphical user interface, simply and easily. It is
implemented as a Python extension module that wraps the GUI components
of the popular wxWidgets cross platform library, which is written in
C++.
wxPython is a cross-platform toolkit. This means that the same program
will usually run on multiple platforms without modifications.
Currently supported platforms are 32-bit Microsoft Windows, most Linux
or other Unix-like systems using GTK2, and Mac OS X 10.3+, in most
cases the native widgets are used on each platform to provide a 100%
native look and feel for the application.
Changes in 2.8.8.1
------------------
wx.richtext: Added wrappers for the RichTextPrinting and
RichTextPrintout classes.
Make it easier to replace the check box images used in the
CheckListCtrlMixin class.
Fixed bug in wx.ScrolledWindow when child focus events caused
unneccessary or incorrect scrolling.
Fixed a bug in wx.GridBagSizer where hidden items were not ignored in
part of the layout algorithm.
Several other bugs also fixed.
Added builds for Ubuntu Hardy (8.04)
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
Is there some change with wx.FileConfig in 2.8.8.1?
I am getting this exception trying to start Boa and this worked with 2.8.8.0 and I just tested with 2.8.7.1 which works too.
Traceback (most recent call last):
File "C:\Python25\Lib\site-packages\boa\Boa.py", line 271, in <module>
import Preferences, Utils
File "C:\Python25\Lib\site-packages\boa\Preferences.py", line 174, in <module>
c = wx.FileConfig(localFilename=file, style= wx.CONFIG_USE_LOCAL_FILE)
File "C:\Python25\Lib\site-packages\wx-2.8-msw-unicode\wx\_misc.py", line 3313
, in __init__
_misc_.FileConfig_swiginit(self,_misc_.new_FileConfig(*args, **kwargs))
wx._core.PyNoAppError: The wx.App object must be created first!
Is there some change with wx.FileConfig in 2.8.8.1?
I am getting this exception trying to start Boa and this worked with 2.8.8.0 and I just tested with 2.8.7.1 which works too.
Traceback (most recent call last):
File "C:\Python25\Lib\site-packages\boa\Boa.py", line 271, in <module>
import Preferences, Utils
File "C:\Python25\Lib\site-packages\boa\Preferences.py", line 174, in <module>
c = wx.FileConfig(localFilename=file, style= wx.CONFIG_USE_LOCAL_FILE)
File "C:\Python25\Lib\site-packages\wx-2.8-msw-unicode\wx\_misc.py", line 3313
, in __init__
_misc_.FileConfig_swiginit(self,_misc_.new_FileConfig(*args, **kwargs))
wx._core.PyNoAppError: The wx.App object must be created first!
I had a bug report of segfaults if wxConfig.Get() was called before the app object was created. This is because it is trying to use the app object to know how to make a default config object. So I added the must-have-app directive to it. Since the plain config classes also use the app object for getting the app name and vendor name I thought it would make sense to also add the directive there, but I see now that it is already checking that the app exists so I guess I didn' need to do that...
I tried the new Adobe Reader 9 using wx.lib.pdfwin.py and everything works just fine, both using wxPython 2.8.8.1 and the earlier version of pdfwin in 2.8.7.x
Unfortunately, only until the app is closed. At which point Python/Pythonw crashes with a memory error. It happens both in my own application and with the wxPython demo. It may or may not be significant that the reported memory locations are the same for both -
Python.exe - Application Error. The instruction at "0x0700609c" referenced memory at "0x00000014". The memory could not be "read"
Using a frozen, py2exe application, it terminates as soon as the pdf reader is loaded.
It seems reasonable to assume that the problem lies with the new reader but is it possible to discover any more about the crash to back this up?
I tried
the new Adobe Reader 9 using wx.lib.pdfwin.py and everything works just
fine, both using wxPython 2.8.8.1 and the earlier version of pdfwin in
2.8.7.x
Unfortunately, only until the app is closed. At which point
Python/Pythonw crashes with a memory error. It happens both in my own
application and with the wxPython demo. It may or may not be
significant that the reported memory locations are the same for both -
Python.exe - Application Error. The instruction at “0x0700609c”
referenced memory at “0x00000014”. The memory could not be “read”
Using a frozen, py2exe application, it terminates as soon as the pdf
reader is loaded.
It seems reasonable to assume that the problem lies with the new reader
but is it possible to discover any more about the crash to back this
up?
As a postscript to my own message,
I just closed down Firefox (2.0.0.16) - something I rarely do -
after displaying a PDF (with Adobe Reader 9 still installed) and got
the same error message as above.
I tried the new Adobe Reader 9 using wx.lib.pdfwin.py and everything works just fine, both using wxPython 2.8.8.1 and the earlier version of pdfwin in 2.8.7.x
Unfortunately, only until the app is closed. At which point Python/Pythonw crashes with a memory error. It happens both in my own application and with the wxPython demo. It may or may not be significant that the reported memory locations are the same for both -
Python.exe - Application Error. The instruction at "0x0700609c" referenced memory at "0x00000014". The memory could not be "read"
Using a frozen, py2exe application, it terminates as soon as the pdf reader is loaded.
It seems reasonable to assume that the problem lies with the new reader but is it possible to discover any more about the crash to back this up?
As a postscript to my own message, I just closed down Firefox (2.0.0.16) - something I rarely do - after displaying a PDF (with Adobe Reader 9 still installed) and got the same error message as above.
Sounds like Adobe has once again "fixed" something so well that it breaks everybody's code...
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
