On 1/26/11 4:57 PM, Terry Reedy wrote:
From what I remember when I looked at the WxWidgets feature list some years
ago, WxWidgets does not come with a scripting language, but also has more that
strictly gui stuff. So I think it would also need to be subsetted.
For what it's worth, wxPython tries not to wrap parts of wxWidgets that can be
replicated by the standard library. I do believe they wrap some non-GUI parts of
wxWidgets that are needed to work with certain GUI widgets, but don't quote me
on that.
On 1/26/2011 11:35 AM, Robert Kern wrote:
There is certainly enough maintenance force to keep wxPython updated and
ported to Python 3, but only *outside* of the standard library.
I got the opposite impression from the link above. As of last May, 3.x support
is deferred until a new C++ code generator is written, and that is deferred
until new features are added and released. So it seems the project needs another
person to either code the new code generator or learn how to port Capi code (or
both). Since there is no 2to3 for Capi (as opposed to Python code), I do not
even know is a single code base is possible. I am sure that whoever works on a
wxPython port could learn from whoever did the numpy port.
In loose terms, what we learned from the experience was that it actually isn't
so bad once you knuckle down to it. But yes, it does look like some more
volunteer effort would be needed to get Python 3 support soon. I note that I did
not specify any particular deadline. :-) I just wanted to disabuse Octavian of
the idea that we are claiming that the wxPython team is inadequate in general.
--
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless enigma
that is made terrible by our own mad attempt to interpret it as though it had
an underlying truth."
-- Umberto Eco
--
http://mail.python.org/mailman/listinfo/python-list
