I noticed the wxPython next generation in the roadmap.
Is there anything write up about what the thinking is on this?
Is this coming for a dislike of swig?
Barry
I noticed the wxPython next generation in the roadmap.
Is there anything write up about what the thinking is on this?
Is this coming for a dislike of swig?
Barry
As Robin mentioned on TentativeRoadmap - wxPyWiki, the
idea is to make it easier to generate the wx bindings so that wxPython
can more easily support both Python 2.x and 3.x.
On Apr 11, 2:15 pm, Barry Scott <ba...@barrys-emacs.org> wrote:
I noticed the wxPython next generation in the roadmap.
Is there anything write up about what the thinking is on this?
Is this coming for a dislike of swig?
Barry
-------------------
Mike Driscoll
I noticed the wxPython next generation in the roadmap.
Is there anything write up about what the thinking is on this?
There are tidbit comments and discussions about it scattered in the archives and such. I've also got some initial goals and design written up here, but it's not ready to publish yet as I was still doing some initial ground-work before making final decisions when I put it on the back burner to get caught up on other things for a while. When I'm able to get back to it I'll try to put that in a form that others can read and discuss.
Is this coming for a dislike of swig?
Only partially. Since there could be quite a bit of shake-up in how things are done I thought it would be wise to look at other tools and see what advantages they may give over what swig provides, and see if it makes sense to make a change there too. But it's not the primary motivating factor.
On 4/11/10 12:15 PM, Barry Scott wrote:
--
Robin Dunn
Software Craftsman
If my PyCXX (cxx.sf.net) can help you let me know.
I have Python 2 and Python 3 support.
Barry
On 12 Apr 2010, at 20:25, Robin Dunn wrote:
On 4/11/10 12:15 PM, Barry Scott wrote:
I noticed the wxPython next generation in the roadmap.
Is there anything write up about what the thinking is on this?
There are tidbit comments and discussions about it scattered in the archives and such. I've also got some initial goals and design written up here, but it's not ready to publish yet as I was still doing some initial ground-work before making final decisions when I put it on the back burner to get caught up on other things for a while. When I'm able to get back to it I'll try to put that in a form that others can read and discuss.
Is this coming for a dislike of swig?
Only partially. Since there could be quite a bit of shake-up in how things are done I thought it would be wise to look at other tools and see what advantages they may give over what swig provides, and see if it makes sense to make a change there too. But it's not the primary motivating factor.
--
To unsubscribe, send email to wxPython-users+unsubscribe@googlegroups.com
or visit http://groups.google.com/group/wxPython-users?hl=en