wammu will work with wxpython-2.8, and I have been running a local version as such for the past month, mainly due to an issue with wxpython-2.6 that prevented it from even starting up. AFAIK, wammu developers do recommend that users upgrade to wxpython-2.8 whenever there is a wxGTK related issue, so I'd suggest we upgrade its dependency once and for all.
Oops. I should be clear that I'm only referring to the latest version of wammu (0.27) that just entered the tree. It'd be silly to touch the old stable version.
Based on setup.py content, upstream is happy with axpython version greater than 2.6.2.0. Do you actually had a problem with wxpython-2.6 + wammu-0.27 combination?
Latest stable wxpython-2.6 with my own wammu-0.27 resulted in the error described in bug #163566. I ended up having to remove the wxversion patch to get it to run. I'm re-emerging wxpython-2.6 right now so I can give you a confirmation later today. Currently wammu has a hard dependency on =wxpython-2.6 with is forced using a gentoo-specific patch. This pulls in a relatively large wxGTK-2.6 even for those that have wx*-2.8 installed.
Result with new installation of wxGTK/wxpython-2.6 with wammu-0.27 from portage: yzhao@awa ~ $ wammu Unhandled exception appeared. If you want to help improving this program, please submit following infomation and description how did it happen to http://bugs.wammu.eu/. Please report in english, otherwise you will be most likely told to translate you report to english later. Before submiting please try searching for simmilar bugs on http://bugs.cihar.com/view_all_set.php?f=3&type=1&search=ee939ba73ce4cf3ec3d94c0e7d1cf46d --------------- System information ---------------- Platform linux2 Python 2.5.2 wxPython 2.6.4.0 Wammu 0.27 python-gammu 0.26 Gammu 1.20.0 Bluetooth PyBluez locales en_CA (UTF8) connection device model ------------------ Traceback ID ------------------- ee939ba73ce4cf3ec3d94c0e7d1cf46d -------------------- Traceback -------------------- File "/usr/bin/wammu", line 109, in <module> Wammu.App.Run() File "/usr/lib/python2.5/site-packages/Wammu/App.py", line 69, in Run app = WammuApp() File "usr/lib/python2.5/site-packages/wx-2.6-gtk2-unicode/wx/_core.py", line 7755, in __init__ File "usr/lib/python2.5/site-packages/wx-2.6-gtk2-unicode/wx/_core.py", line 7407, in _BootstrapApp File "/usr/lib/python2.5/site-packages/Wammu/App.py", line 50, in OnInit frame = Wammu.Main.WammuFrame(None, -1) File "/usr/lib/python2.5/site-packages/Wammu/Main.py", line 238, in __init__ self.rightwin.sizer.Add(self.righttitle, 0, wx.LEFT|wx.ALL|wx.EXPAND, self.separatorNormal) File "usr/lib/python2.5/site-packages/wx-2.6-gtk2-unicode/wx/_core.py", line 11766, in Add -------------------- Exception -------------------- TypeError: wx.Window, wx.Sizer, wx.Size, or (w,h) expected for item --------------------------------------------------- Error does not occur if I remove the line "wxversion.select(['2.6'])" from /usr/bin/wammu or change it to 2.8.
On my box I have wxpython-2.6.4.0-r1 and in my case wammu doesn't crash at startup, as in your case. wxwidgets team, please advise.
it looks like you're hitting bug #163566 which to be honest has me stumped.
(In reply to comment #6) > it looks like you're hitting bug #163566 which to be honest has me stumped. Bummer. In that case, can we change wammu-0.27 to depend on >=wxpython-2.6, remove the wxversion patch, and call it a day?
Created attachment 163232 [details] wammu-0.28.ebuild with wxpython-2.8 dependency wammu didn't work for me with the older wxpython, so I have modified the 0.27 ebuild: raised the dependency to wxpython-2.8 removed check for unicode use flag (which isn't present in new wxpython ebuilds) bumped version to more recent wammu-0.28 I'm no expert in writing ebuilds, but it seems to work fine here.
Fixed in wammu-0.28. For some reason, it failed to work when I patched it with wammu-wxversion.patch, so I dropped it in this version and I changed the wxpython dependency atom to >=dev-python/wxpython-2.8 .
Working well. Thanks.