Jump to content

wxPython

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Brylie (talk | contribs) at 10:25, 7 August 2017 (Add 4.0.0b1 preview release). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Developer(s)Robin Dunn
Harri Pasanen
Initial release1998; 26 years ago (1998)[1]
Stable release
3.0.2.0 / November 28, 2014; 9 years ago (2014-11-28)
Preview release
4.0.0b1 (Phoenix)[2]
Repository
Written inC++ / Python
Operating systemCross-platform
LicensewxWindows License
Websitewxpython.org

wxPython is a wrapper for the cross-platform GUI API (often referred to as a "toolkit") wxWidgets (which is written in C++) for the Python programming language. It is one of the alternatives to Tkinter, which is bundled with Python. It is implemented as a Python extension module (native code). Other popular alternatives are PyGTK, its successor PyGObject and PyQt. Like wxWidgets, wxPython is free software.

License

Being a wrapper, wxPython uses the same free software licence used by wxWidgets (wxWindows License)[3]—which is approved by Free Software Foundation and Open Source Initiative.

History

wxPython was created when Robin Dunn needed a GUI to be deployed on HP-UX systems and also on Windows 3.1 within a few weeks. While evaluating commercial solutions, he ran across Python bindings for the wxWidgets toolkit. Thus, he learned Python and, in a short time, together with Harri Pasanen, became one of the main developers of wxPython, which grew from those initial bindings.

The first versions of the wrapper were created by hand. However, soon the code base became very difficult to maintain and keep synchronized with wxWidgets releases. Later versions were created with SWIG, greatly decreasing the amount of work to update the wrapper. The first "modern" version was announced in 1998.[1]

Example

This is a simple "Hello world" module, depicting the creation of the two main objects in wxPython (the main window object and the application object), followed by passing the control to the event-driven system (by calling MainLoop()) which manages the user-interactive part of the program.

#!/usr/bin/env python
import wx

app = wx.App(False)  # Create a new app, don't redirect stdout/stderr to a window.
frame = wx.Frame(None, wx.ID_ANY, "Hello World") # A Frame is a top-level window.
frame.Show(True)     # Show the frame.
app.MainLoop()

Project Phoenix

Project Phoenix, which began in 2010, is an effort to clean up the wxPython implementation and in the process make it compatible with Python 3.[4] This project is a new implementation of wxPython, focused on improving speed, maintainability and extensibility. Just like "Classic" wxPython, it wraps the wxWidgets C++ toolkit and provides access to the user interface portions of the wx API, enabling Python applications to have a graphical user interface on Windows, Mac or Unix systems with a native look and feel and requiring very little, if any, platform-specific code.[5]

Applications Developed with wxPython

See also

References

Notes
  1. ^ a b "wxPython 0.3 announcement on Yahoo Groups". Retrieved 2007-01-16.
  2. ^ "wxPython 4.0.0b1 Released". Retrieved 2017-08-07.
  3. ^ "Copyright notice". Retrieved 2009-02-27.
  4. ^ "Goals of Project Phoenix". Retrieved 2016-03-17.
  5. ^ "Project Phoenix readme file on GitHub". Retrieved 2014-01-01.
  6. ^ "Open source components and licenses". Google. Retrieved 28 January 2013.
Bibliography

Further reading