ANN: wxPython 2.9.5.0

773 views
Skip to first unread message

Robin Dunn

unread,
Sep 2, 2013, 11:14:17 PM9/2/13
to wxpytho...@googlegroups.com, wxpyth...@googlegroups.com, wx-u...@googlegroups.com, wx-an...@googlegroups.com, python-ann...@python.org
Announcing
----------

wxPython 2.9.5.0 (classic) has been released and is now available for
download at http://wxpython.org/download.php. There have been a few
enhancements and additions, and lots of bugs fixed. More details are
below.

Various binaries are available for 32-bit and 64-bit Windows, and also
for OSX using the Carbon and Cocoa APIs, for Python 2.6 and 2.7.
Source code is also available at http://wxpython.org/download.php of
course, for building your own.


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 set of Python extension modules that wrap 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 and 64-bit Microsoft Windows,
most Linux or other Unix-like systems using GTK2, and Mac OS X 10.4+.
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.9.5.0
------------------

wx.media.MediaCtrl on OSX-cocoa now has a functioning back-end using
the QTKit framework, so it works when running in either 32-bit or
64-bit mode.

Printing triggered from a Javascript window.print() statement will now
work on OSX when using the old wx.webkit or the new wx.html2 browser
controls.

Updated Scintilla code to verison 3.21

Lots of fixes and improvements in the wxWidgets code.

Changed the wx.DateTime.Parse* methods to work like they did in
wxPython 2.8, they now return an integer indicating how far in to
the string that the parser parsed, or -1 on error.

Updated wx.lib.pdfviewer with patches from David Hughes.


--
Robin Dunn
Software Craftsman
http://wxPython.org

Metallicow

unread,
Sep 2, 2013, 11:15:18 PM9/2/13
to wxpytho...@googlegroups.com, wxpyth...@googlegroups.com, wx-u...@googlegroups.com, wx-an...@googlegroups.com, python-ann...@python.org
Wooooooot!

Metallicow

unread,
Sep 3, 2013, 12:46:09 AM9/3/13
to wxpytho...@googlegroups.com, wxpyth...@googlegroups.com, wx-u...@googlegroups.com, wx-an...@googlegroups.com, python-ann...@python.org
While 'We' are here. Users should make suggestions/TODO for Robins next release.

This should be a TODO.txt/Wishlist.txt list for Robin included in src or where-ever.
For Users suggestion and sutch....

~Professionalism-1stAndForemost
  [ ] Trim Trailing Space(On Everything.-Yes You Reading This!).
  [ ] Trim Trailing Space Again(On Everything.-Yes You Reading This!).
  [ ] Update Readmes.
  [ ] DEV: Update Changelog More(We like the nitty details).
  [ ] Try to PEP8 everything(as you go...) for Zen: Readability.
  [ ] Keep consistent with the codeing guidelines.txt. Grammar and Punctuation. Periods REQUIRED for comment lines.
  [ ] Set a standard for comments.
  [X] I'll think of it now(later).
~Fixes
  [ ] Thumbnailer lowercasing issue(If not already fixed).
  [ ] PlateButton Issues(Update from Editra lib).
~Updates
  [ ] Update Scintilla. This keeps Devs wxDevving.
  [ ] PDF Stuff.
  [ ] Media/ActiveX Stuff


Thanks for the RELz Robin!

Metallicow

unread,
Sep 3, 2013, 1:29:51 AM9/3/13
to wxPyth...@googlegroups.com, wxpytho...@googlegroups.com, wxpyth...@googlegroups.com, wx-u...@googlegroups.com, wx-an...@googlegroups.com, python-ann...@python.org
To Add to the TODO.txt/Wishlist.txt....

~Verified OS's (minimum)
 [ ] Win 2000
 [ ] Win XP Pro 32 bit
 [ ] Macintosh(Stick the least req ver) / OSX
 [ ] Ubuntu/Kubuntu/Mandriva/Mageia/OtherLinux(Stick the least req ver)
 [ ] Other. Add Here.

Mario Lacunza

unread,
Sep 3, 2013, 1:53:26 AM9/3/13
to wxpytho...@googlegroups.com
Hi

Any chance to obtain an Ubuntu package?

Saludos / Best regards

Mario Lacunza
Email:: mlac...@gmail.com
Personal Website:: http://www.lacunza.biz/
Hosting:: http://mlv-host.com/
Mascotas Perdidas:: http://mascotas-perdidas.com/
Google Talk / Y! messenger / Skype: mlacunzav
MSN: mlac...@hotmail.com

El 02/09/13 22:14, Robin Dunn escribió:

Tim Roberts

unread,
Sep 3, 2013, 1:55:20 PM9/3/13
to wxpytho...@googlegroups.com
Metallicow wrote:
> To Add to the TODO.txt/Wishlist.txt....
>
> ~Verified OS's (minimum)
> [ ] Win 2000
> [ ] Win XP Pro 32 bit

Windows 2000 is simply no longer relevant for new releases. If you're
running Windows 2000, you can live with an older wx release. After all,
do you expect Robin to issue verified releases for Linux 2.0.37? That's
the Linux equivalent of Windows 2000.

Sadly, Windows XP is just about to fall into the "no longer relevant"
category as well.

--
Tim Roberts, ti...@probo.com
Providenza & Boekelheide, Inc.

Metallicow

unread,
Sep 3, 2013, 2:37:04 PM9/3/13
to wxpytho...@googlegroups.com


On Tuesday, September 3, 2013 12:55:20 PM UTC-5, Tim Roberts wrote:

Windows 2000 is simply no longer relevant for new releases.  If you're
running Windows 2000, you can live with an older wx release.  After all,
do you expect Robin to issue verified releases for Linux 2.0.37?  That's
the Linux equivalent of Windows 2000.

Sadly, Windows XP is just about to fall into the "no longer relevant"
category as well.

No, I don't expect it to work on every OS. Basically just a user reference checklist of OS's that have been tested in a virtual machine. If wx version release #.#.# works on OS *name* add a check to the list.
For example if a simple 2.9.5 frame app fires up on win98, add a [X] Win98 checkmark box to the verified OS's.
I routinely check my app on various OS and place that info with my documentation.
Sorry if that came across as 'it absolutely needs to work on OS'. Not the intention. Just for reference.

Well, as far as XP, I think most user's still using XP won't care to switch for at least 10 more years or maybe more, Even if MS is retiring it.
Until the last piece of CPU that can run it is tossed in the landfill, it will always be around, in one form or another(virtual). But Yes, it is sad that it's support life will be dead next year.

edoc

unread,
Sep 4, 2013, 10:05:25 PM9/4/13
to wxpytho...@googlegroups.com
It's true.  Windows XP is the new MS-DOS 6.22 :)


--
You received this message because you are subscribed to the Google Groups "wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wxpython-user...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Metallicow

unread,
Sep 5, 2013, 3:46:08 AM9/5/13
to wxpytho...@googlegroups.com


On Wednesday, September 4, 2013 9:05:25 PM UTC-5, edoxtator wrote:
It's true.  Windows XP is the new MS-DOS 6.22 :)

No, not quite; But it gets a point for a nostalgia laugh.

I still have the oldie rigs laying around, and yes, it is still operational(setting next to the OrangeBox). Classic Win 3.1. *Time to fire that puppy up again...*
I still put old HDs/Hardware to use. And last I checked, Museums/Educational Institutions/Recycling Centers do also.
:)

Metallicow

unread,
Sep 5, 2013, 4:10:15 AM9/5/13
to wxpytho...@googlegroups.com

Wow. Vibration *Silicone-like Stuff* wrapping the HDD.
Cant read it much of the label..., but I have another 4GB like it and they will last(almost forever).
Too bad they don't make HDD like that nowadays.
The only things that could be improved upon them are HDDspeed, HDDsize, and connectors(IDE, SATA, etc) for the most part.
*Geez, where did they manufacture this stuff at... might be a home-brew mold also....*
:)

Marco Prosperi

unread,
Sep 6, 2013, 5:02:27 AM9/6/13
to wxPyth...@googlegroups.com, wxpytho...@googlegroups.com, wxpyth...@googlegroups.com, wx-u...@googlegroups.com, wx-an...@googlegroups.com, python-ann...@python.org

when I close my application I get this (win7-64, py2.7, wxpy 2.9.5-32bit). Didn't happen with wxpy 2.9.4

swig/python detected a memory leak of type 'wxPyXmlSubclassFactory *', no destru
ctor found.
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
  File "C:\Program Files (x86)\Python27\lib\atexit.py", line 24, in _run_exitfun
cs
    func(*targs, **kargs)
PyAssertionError: C++ assertion "GetEventHandler() == this" failed at ..\..\src\
common\wincmn.cpp(468) in wxWindowBase::~wxWindowBase(): any pushed event handle
rs must have been removed
Error in sys.exitfunc:
Traceback (most recent call last):
  File "C:\Program Files (x86)\Python27\lib\atexit.py", line 24, in _run_exitfun
cs
    func(*targs, **kargs)
wx._core.PyAssertionError: C++ assertion "GetEventHandler() == this" failed at .
.\..\src\common\wincmn.cpp(468) in wxWindowBase::~wxWindowBase(): any pushed eve
nt handlers must have been removed

niki

unread,
Sep 12, 2013, 5:48:41 AM9/12/13
to wxpytho...@googlegroups.com
Thanks for the new version!

I fond a small issue:

python2.7/win32

swig/python detected a memory leak of type 'wxPyXmlSubclassFactory *',
no destructor found.

regards,

Niki

Robin Dunn

unread,
Sep 12, 2013, 9:47:31 PM9/12/13
to wxpytho...@googlegroups.com
Yep, this is known. It is safe to ignore for now, and there will be a
proper fix before the next release.

Aaron O'leary

unread,
Dec 13, 2014, 11:30:26 AM12/13/14
to wxpytho...@googlegroups.com
Hi Robin,

I have the same issue as Niki,

"swig/python detected a memory leak of type 'wxPyXmlSubclassFactory *', no destructor found"

Any update on the solution?

I'm not sure what you mean by 'safe to ignore for now' - how would I go about ignoring this error?

Thanks,
aaron

Werner

unread,
Dec 13, 2014, 4:45:29 PM12/13/14
to wxpytho...@googlegroups.com
On 12/13/2014 17:30, Aaron O'leary wrote:
> Hi Robin,
>
> I have the same issue as Niki,
>
> "swig/python detected a memory leak of type 'wxPyXmlSubclassFactory
> *', no destructor found"
>
> Any update on the solution?
I am not sure but wouldn't be surprised if 3.0 has resolved this issue.

Can you upgrade to 3.0.1 or even better to 3.0.2 and test it.

Werner

Aaron O'leary

unread,
Dec 14, 2014, 1:47:50 PM12/14/14
to wxpytho...@googlegroups.com
I am not sure but wouldn't be surprised if 3.0 has resolved this issue.

Can you upgrade to 3.0.1 or even better to 3.0.2 and test it.



3.0.2 fixes the issue.

I'm using Anaconda, which comes with a build of 3.0.0, so I was looking for a workaround.

I've now worked out how to build my own 3.0.2.0 for anaconda and have put the build on binstar:

https://binstar.org/aaren/wxpython

My build recipe is here:

https://github.com/aaren/conda-recipes/tree/wxpython-3.0.2/wxpython

(used with `conda build`)

I've detailed the build in the pull-request: https://github.com/conda/conda-recipes/pull/217

Notably, there was some weirdness related to g++44 (which I had to pretend was on my system by symlinking it to g++).

Now that I've got 3.0.2.0 running on linux I am getting the same error with my code as with my Windows install, which I'm taking as reassurance that I've got the build right!

Chris Barker

unread,
Dec 15, 2014, 2:51:50 PM12/15/14
to wxpython-users
On Sun, Dec 14, 2014 at 10:47 AM, Aaron O'leary <aaron....@gmail.com> wrote:
I've now worked out how to build my own 3.0.2.0 for anaconda and have put the build on binstar:

You are awesome, thanks! I need OS-X, but really wanted a recipe to start with, so I didn't have to start from scratch!

-Chris
 

--

Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

Chris....@noaa.gov
Reply all
Reply to author
Forward
0 new messages