This is just a quick post to let everyone know that the previous post in this blog, Building wxPython for Linux via Pip has been updated to include a simple set of build steps detailing how you can build your own wxPython wheel on Linux or other Unix-like systems.
[ Post updated 2018-02-03, see new Build Steps section below. ]
wxPython Wheels for Linux?
Before reading further, you may want to check and see if there are already some wxPython wheels available for your flavor of Linux. A few are built as part of the release process and are available from one of wxPython's servers. More details and some links are on the download page.
If there are no existing wheels there for your distro, (or perhaps a close relative,) then read on to find out why we can't just provide wheels for all Linuxes, and what you need to build one for yourself.
There have been some issues flowing into Phoenix's issue tracker since the release of wxPython 4.0.0b1 related to installation issues on Linux using pip, which have caused some overhead and soaked up unnecessary amounts of time. So lets start with getting some of the basics out of the way. There are a lot of flavors of linux. To name a few there's the Debian family, Debian, Ubuntu, Kubuntu, Elementary, Mint, etc., Arch, Gentoo, RHEL and CentOS, and so on. Each flavor has differences which can make binary distributions incompatible across flavors.
Why does this affect wxPython you may ask? It's just a Python package, and Python source is independent across operating systems after all, right?. Well, not all Python packages are just Python. wxPython as an example contains binary extension modules (compiled C or C++ code that is platform and architecture dependent.) wxPython by default also contains a copy of the compiled version of the wxWidgets library written in C++, which also depends on other 3rd party libraries which need to not only be present at runtime, but also have their development-related files present at wxWidgets' and wxPython's compile time.
Pip in its infinite wisdom can detect this, and knows how to select the appropriate binary wheel for the following criteria:
- OS (Windows, macOS, Linux)
- Architecture (i386, x86_64, etc)
- Python Version (2.7, 3.5, 3.6, etc)
See how pip doesn't care about the specific linux distribution? That's the
issue. The binary content and dependencies of wxPython can't be delivered
consistently via pip. There are some efforts to get around this (eg. PEP
they don't quite work for wxPython yet. Packages that are able to fit into
the very narrow
manylinux1 requirements can be hosted on PyPI and will
install with pip just as smoothly as pure-python packages do. Unfortunately
manylinux1 spec does not include a version of GTK+ and its
dependencies that are new enough to be able to provide all the features
that wxWidgets requires.
In order to deploy to linux systems wxPython4 (Phoenix) simply builds itself from a source tarball as part of the pip setup process. All of the code generated by wxPython's build system is already present in the tarball, it merely needs to be compiled. This causes a very lengthy installation times, but is a necessary evil. Because the build is just that, a build, you will need all of wxWidgets and wxPython's binary dependencies present at build time. wxWidgets' configure will be run, and if it detects missing libraries the whole build, and therefore the pip installation, will fail.
What You Need
You will need the following packages (please consult your distribution's package list for the appropriate package names) and their dependencies:
- python-dev (for your version of python)
- gtk (preferably version 3, but depends on your needs)
- libwebkitgtk (matching your gtk version)
on Debian based systems, or other systems that separate development
packages from standard packages, you will need the corresponding
-devel package in addition to the standard package.
Once the appropriate packages are present on your system then wxPython should build with no problems, either with pip or from a source tree extracted from the source tarball. If it still doesn't work for you then be sure to look closely at the build log as there will likely be some clues there that may point you in the right direction. For example, this:
checking for OpenGL headers... not found checking for GL/gl.h... no configure: error: OpenGL libraries not available
will tell you that the OpenGL libraries are missing. They are usually a dependency of the glut or freeglut packages and should have been installed along with that library, but perhaps your system's dependencies are different and you'll need to do a little investigation to determine the proper system packages that need to be installed.
Once you have installed the required depenency libraries, it should take just a few steps to build a wxPython that will work on your system with your Python. The steps shown here are just one option, but seems to be one of the simpler approaches to take, and will require nothing extra to be installed in your system Python. These instructions assume that you will be using a 3.4+ version of Python and that the executable is called "python3". If you are using 2.7 or the binary is called something else then adapt accordingly.
Step 1: The first thing we'll do is create and activate a new virtual environment for the build and the initial testing. This is optional, but highly recommended as it will ensure that there is nothing left over from a previous build that could trip things up. The last two commands shown here are just so you can verify that the python and pip commands are now being found in the new virtual environment instead of from the system or other Python environment.
cd [some tmp folder] python3 -m venv builder_py source builder_py/bin/activate which python which pip
Step 2: Next, you'll want to update pip and add a few more packages.
pip install -U pip pip install -U six wheel setuptools
Step 3: Use pip to download the latest source archive from PyPI.
pip download wxPython
Step 4: Use pip to build a wxPython wheel file. We'll also redirect the build output to a file so you can review it later if needed. This step will take a while to complete, as it will be compiling all the wxWidgets and wxPython source code, but you'll be able to watch the build output to monitor the progress. Be sure to use the actual name of the downloaded source archive file, which may be different than the one shown here.
pip wheel -v wxPython-4.0.1.tar.gz 2>&1 | tee build.log
Step 5: If the build was successful then you should now have a wxPython
wheel file in the current working directory. If there was a problem then
build.log file and see if you can spot any clues as to what
dependencies may be missing or out of date. (Build problems from wxPython
release sources are almost always due to missing dependencies.) Once you
think you have solved the problem go back to step 4 and try the build
Step 6: The next step is to install the wheel file in the virtual environment and give it a quick test run. (Use the actual name of the wheel file you built, which may be different than the one shown here.)
pip install wxPython-4.0.1-cp35-cp35m-linux_x86_64.whl python -c "import wx; a=wx.App(); wx.Frame(None,title='hello world').Show(); a.MainLoop();"
You should see a new window open with a "hello world" title bar, which will indicate that this build was successful and this wxPython wheel can be used on your system. You can now use pip to install the wheel file in other Python environments or virtual environments that use the same base Python executable that you used for this build.
Q1: "Why can't you just install the necessary packages as part of wxPython's installation"
A1: Lots of good reasons, among them are: Pip is NOT your linux package manager, Phoenix is not responsible for maintaining your system.
Q2: "I can install PyQt(4/5) just fine via pip! Why can't wxPython do the same?"
A2: Qt does not depend on system provided libraries other than the low- level basic libs. wxWidgets does, it's one of the defining differences of the two toolkits. As such PyQt can deliver to all linuxes in the same manner.
For the past few months I have been working for Enthought and helping out with a new upcoming product. Since that is about to transition to a more long term employment opportunity for me I figured it would be a good idea to let the wxPython community know about it, and also to let you know about some aspects of the job that some may find a little surprising, before you hear about it as rumors or gossip.
We'll miss you Neil. Breathe free. Fly high.
Watch as the Phoenix spreads her wings over Python 3:
My current long-term consulting project will be coming to an end soon, so I am currently looking for some short-term paying projects to fill in while I'm looking for my next long-term gig. Anything ranging from a few days to several weeks worth of work would be fine. So if you would like some help with your wx-related projects, would like to have specific bugs fixed or new features added to wxWidgets or wxPython, or would like to sponsor some of my work on Phoenix, then please send me an email and we can discuss the details.
Of course if you have or know of a long-term position available that would fit my skill set then please let me know about that as well.
Several months ago Microsoft had an ad campaign where they would have an average Joe or Jane talk about some cool wizbang feature of Windows 7 and how it was all their idea. It was one of Microsoft's better ad campaigns, and was actually understandable by the average person without requiring the viewer to know industry inside jokes, or to understand Jerry Seinfeld, to be able to "get" the gist of the commercial. It also employed some cute gimmicks, such as when the person was remembering back to how they thought up the wonderful new idea the directors used a different actor who was younger, thinner, cuter, handsomer, and had way better hair than the real person.