py26-wxpython: update to 2.8.12.0

[howarth@…]

Currently the wxWidgets-python/py26-wxpython packaging is too old to support the new GUI interface in the relax 1.3.10 update I have prepared. The attached packaging updates the existing py26-wxpython to 2.8.12.0.

[howarth@…]

update Portfile diff for py26-wxpython 2.8.12.0

[howarth@…]

FYI, I don't see anyway to add the cc for the maintainer to a ticket after it is created. Is this a defect in the web design?

[ryandesign (Ryan Carsten Schmidt)]

I do not remember what the limitations are for regular Trac users, since I have had elevated Trac privileges for awhile. I've assigned the ticket to the port's maintainer for you.

[jjstickel@…]

Cc Me!

[jjstickel@…]

This patch worked for me with the +gtk variant. Tested with py26-matplotlib and py26-mayavi.

[mf2k (Frank Schima)]

I see the following error, also with the +gtk variant.

:info:build /usr/bin/gcc-4.2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -arch x86_64 -DSWIG_TYPE_TABLE=_wxPython_table -DSWIG_PYTHON_OUTPUT_TUPLE -DWXP_USE_THREAD=1 -UNDEBUG -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXGTK__ -D_REENTRANT -Iinclude -Isrc -I/opt/local/lib/wx/include/gtk2-unicode-release-2.8 -I/opt/local/include/wx-2.8 -I/opt/local/include/gtk-2.0 -I/opt/local/lib/gtk-2.0/include -I/opt/local/include/atk-1.0 -I/opt/local/include/cairo -I/opt/local/include/gdk-pixbuf-2.0 -I/opt/local/include/pango-1.0 -I/opt/local/include/gio-unix-2.0/ -I/opt/local/include -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include/pixman-1 -I/opt/local/include/freetype2 -I/opt/local/include/libpng14 -I/opt/local/Library/Frameworks/Python.framework/Versions/2.6/include/python2.6 -c src/gtk/_misc_wrap.cpp -o build-gtk2.unicode/temp.macosx-10.6-x86_64-2.6/src/gtk/_misc_wrap.o -O3
:info:build cc1plus: warning: command line option "-Wstrict-prototypes" is valid for C/ObjC but not for C++
:info:build src/gtk/_misc_wrap.cpp: In function 'void SWIG_Python_AddErrorMsg(const char*)':
:info:build src/gtk/_misc_wrap.cpp:864: warning: format not a string literal and no format arguments
:info:build In file included from src/gtk/_misc_wrap.cpp:2740:
:info:build include/wx/wxPython/wxPython.h: In function 'bool wxPyCoreAPI_IMPORT()':
:info:build include/wx/wxPython/wxPython.h:39: warning: deprecated conversion from string constant to 'char*'
:info:build include/wx/wxPython/wxPython.h:39: warning: deprecated conversion from string constant to 'char*'
:info:build src/gtk/_misc_wrap.cpp: In function 'PyObject* _wrap_GetElapsedTime(PyObject*, PyObject*, PyObject*)':
:info:build src/gtk/_misc_wrap.cpp:4977: warning: 'wxGetElapsedTime' is deprecated (declared at /opt/local/include/wx-2.8/wx/stopwatch.h:77)
:info:build src/gtk/_misc_wrap.cpp:4977: warning: 'wxGetElapsedTime' is deprecated (declared at /opt/local/include/wx-2.8/wx/stopwatch.h:77)
:info:build src/gtk/_misc_wrap.cpp: In function 'PyObject* _wrap_StartTimer(PyObject*, PyObject*)':
:info:build src/gtk/_misc_wrap.cpp:5080: warning: 'wxStartTimer' is deprecated (declared at /opt/local/include/wx-2.8/wx/stopwatch.h:73)
:info:build src/gtk/_misc_wrap.cpp:5080: warning: 'wxStartTimer' is deprecated (declared at /opt/local/include/wx-2.8/wx/stopwatch.h:73)
:info:build src/gtk/_misc_wrap.cpp: In function 'PyObject* _wrap_DateTime_SetToTheWeek(PyObject*, PyObject*, PyObject*)':
:info:build src/gtk/_misc_wrap.cpp:25372: warning: 'SetToTheWeek' is deprecated (declared at /opt/local/include/wx-2.8/wx/datetime.h:737)
:info:build src/gtk/_misc_wrap.cpp: In function 'PyObject* _wrap_DateTime_GetWeek(PyObject*, PyObject*, PyObject*)':
:info:build src/gtk/_misc_wrap.cpp:25435: warning: 'GetWeek' is deprecated (declared at /opt/local/include/wx-2.8/wx/datetime.h:740)
:info:build src/gtk/_misc_wrap.cpp: In function 'void init_misc_()':
:info:build src/gtk/_misc_wrap.cpp:42067: error: 'wxSYS_COLOUR_LISTBOXHIGHLIGHTTEXT' was not declared in this scope
:info:build error: command '/usr/bin/gcc-4.2' failed with exit status 1
:info:build shell command " cd "/opt/local/var/macports/build/_opt_mports_trunk_dports_python_py26-wxpython/py26-wxpython/work/wxPython-src-2.8.12.0/wxPython" && /opt/local/Library/Frameworks/Python.framework/Versions/2.6/bin/python2.6 setup.py build UNICODE=1 WXPORT=gtk2 " returned error 1
:error:build Target org.macports.build returned: shell command failed (see log for details)

[jmroot (Joshua Root)]

Note that this depends on #29389.

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.

[jjstickel (Jonathan Stickel)]

Replying to 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.

[jyrkiwahlstedt]

Replying to jjstickel@…:

Replying to 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:)

[jjstickel (Jonathan Stickel)]

Cc Me!

[mojca (Mojca Miklavec)]

py-wxpython-2.8 is using version 2.8.12.1 (r110279).