1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
|
wxPython 4.0 (Phoenix) for Debian
=================================
The following packages are potentially built from the wxpython4.0 source
package:
python-wxgtk4.0 Python 2 binding to wxGTK
python-wxgtk-media4.0 Python 2 binding to wxGTK media module
python-wxgtk-webview4.0 Python 2 binding to wxGTK webview (html2) module
python3-wxgtk4.0 Python 3 binding to wxGTK
python3-wxgtk-media4.0 Python 3 binding to wxGTK media module
python3-wxgtk-webview4.0 Python 3 binding to wxGTK webview (html2) module
Note about Python 2 packages
----------------------------------------------
In Debian, there are now two sets of Python 2 bindings to wxGTK:
python-wxgtk3.0 (wxPython Classic) and python-wxgtk4.0 (wxPython Phoenix).
Because the two versions are not drop-in replacements for each other,
python-wxgtk3.0 remains the default version for Python 2 and is the only
version available via "import wx".
As the main motivation for wxPython Phoenix is Python 3 support, it is not
expected that any Debian packages will use the Python 2 version of Phoenix.
The expected main use of the Python 2 packages is to allow developers porting
from Python 2/Classic to Python 3/Phoenix to be able to port to
Python 2/Phoenix as an intermediate step.
The Python 2 packages are thus packaged as an egg to avoid conflicting with the
Classic packages. In order to use them, you must change sys.path to include
the egg's path. Example:
$ python2
Python 2.7.15 (default, May 1 2018, 05:55:50)
[GCC 7.3.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> sys.path.insert(0, '/usr/lib/python2.7/dist-packages/wxPython-4.0.1-py2.7-linux-amd64.egg')
>>> import wx
>>> wx.VERSION
(4, 0, 1, '')
>>>
|
