| 1 |
On 9/17/18 5:02 PM, Grant Edwards wrote: |
| 2 |
> |
| 3 |
> It wants to re-install wxpython-3.0.2.0, wxGTK-3.04 and |
| 4 |
> wxGTK-304-r300. I've already done that a few times, but I answered |
| 5 |
> 'y' anyway and let it reinstall them again. It didn't help: |
| 6 |
> |
| 7 |
> $ python -c "import wx" |
| 8 |
> |
| 9 |
> /usr/lib64/python2.7/site-packages/wx-3.0-gtk2/wx/_core.py:16629: UserWarning: wxPython/wxWidgets release number mismatch |
| 10 |
> warnings.warn("wxPython/wxWidgets release number mismatch") |
| 11 |
> |
| 12 |
|
| 13 |
It needs to be version bumped. https://bugs.gentoo.org/632602 |
| 14 |
|
| 15 |
The current version of wxPython is actually 4.0.x and is not compatible |
| 16 |
with wxGTK 3.0.4. wxGTK needs to be bumped as well |
| 17 |
https://bugs.gentoo.org/577030 but there are some breaking changes in |
| 18 |
3.1 vs 3.0. |
| 19 |
|
| 20 |
wxPython 3.0.2.0 is considered 'classic' and was released in 2014. |
| 21 |
|
| 22 |
I tried to use a virtualenv with system package access and tried `pip |
| 23 |
install wxpython` but the oldest sane version you can go back to 4.0.3 |
| 24 |
which won't build with 3.0.4 version of wxGTK. |
| 25 |
|
| 26 |
This discrepancy between the two does not look like it will be fixed any |
| 27 |
time soon. |
| 28 |
|
| 29 |
Andrew |
Archives