#29390: py26-wxpython: update to 2.8.12.0 --------------------------------------+------------------------------------- Reporter: howarth@… | Owner: jameskyle@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: haspatch | Port: py26-wxpython --------------------------------------+------------------------------------- Comment(by jwa@…): Replying to [comment:7 jjstickel@…]:
Replying to [comment:6 jmr@…]:
I'm unclear on why py26-wxpython depends on wxWidgets-python but all other py*-wxpython ports depend on wxWidgets. In fact, I'm unclear on why wxWidgets-python even exists. In any case, it seems like they should all work the same way, which would allow them to be completely unified.
Please see #24350 for a full explanation and the history of the creation of wxwidgets-python. Basically, incremental version updates to wxpython may not be in sync with vanilla wxwidgets (e.g. wxpython-2.8.12.1 may or may not work with wxwidgets-2.8.12). The likely reason py[!26]-wxpython do not depend on wxwidgets-python is because the portfile editors/maintainers do not know this and have gotten away with it so far, but at some point, things will break.
If I were currently using wxwidgets/wxpython, I would gladly provide patches. I am waiting for stable 64-bit cocoa support and am using py-qt4 in the meantime.
Actually, I had a lengthy mail discussion about this with Robin Dunn, because it really doesn't make much sense to require people to have a different wxWidgets only in order to have wxPython, so there should always be a stable wxPython for a stable wxWidgets (the different wxPython releases are usually minor tweaks only, though one has to admit that wxWidgets team has not been the fastest on Earth to deliver new releases:) -- Ticket URL: <https://trac.macports.org/ticket/29390#comment:8> MacPorts <http://www.macports.org/> Ports system for Mac OS