Re: Phoenix Dev Stuff
Scott Talbert <[email protected]>
| Newsgroups | gmane.comp.python.wxpython.devel |
|---|---|
| Message-ID | <[email protected]> |
On Fri, 22 Jul 2016, Robin Dunn wrote: >>>> 3) Is there a reason you're using a separate branch of wxWidgets and not >>>> the WX_3_0_BRANCH? It would seem that if any fixes are needed for >>>> Phoenix, they ought to just go right upstream. >>> >>> It started with one patch that was not getting any attention from the wx >>> dev, and then as I fell behind on my wx mail lists and stuff it was just >>> easier to keep adding things to my own branch and merging WX_3_0_BRANCH >>> into it periodically. I do plan on getting it all merged in eventually >>> however. >> >> Don't you have commit rights to wxWidgets? If so, couldn't you just make >> your fixes directly to WX_3_0_BRANCH? > > I do, and I will work on merging them at latest by the time Phoenix is ready > for alpha, but there is a little more to it than that. Some of the changes > will need discussion on wx-dev, some will need further polishing, and most > will need to be ported to the master branch as well. So yes, it will happen, > but I'd rather wait until I can focus on that effort like I am focusing on > Phoenix now. Actually, I'm more concerned about the changes making it into wxWidgets 3.0.3, which is supposedly coming soon (although it has been in that state for a while). Distributions don't generally use the bundled wxWidgets, so the less patches that have to be applied, the better. Scott