| WxPython | |
|---|---|
 | |
| Developers | Robin Dunn Harri Pasanen |
| Initial release | 1998; 28 years ago (1998) |
| Stable release | |
| Written in | C++ /Python |
| Operating system | Cross-platform |
| License | wxWindows License |
| Website | wxpython |
| Repository | |
wxPython is awrapper for thecross-platformGUIAPI (often referred to as a "toolkit")wxWidgets (which is written inC++) for thePython programming language. It is one of the alternatives toTkinter. It is implemented as a Python extension module (native code).
In 1995, Robin Dunn needed aGUI application to be deployed onHP-UX systems but also runWindows 3.1 within short time frame. He needed across-platform solution. While evaluating free and commercial solutions, he ran acrossPython bindings on the wxWidgets toolkitwebpage (known as wxWindows at the time). This was Dunn's introduction to Python. Together with Harri Pasanen and Edward Zimmerman hedeveloped those initial bindings into wxPython 0.2.[2]
In August 1998, version 0.3 of wxPython was released. It was built for wxWidgets 2.0 and ran on Win32, with a wxGTK version in the works.[3]
The first versions of the wrapper were created by hand. However, thecode became difficult to maintain and keep synchronized with wxWidgets releases. By 1997, versions were created withSWIG, greatly decreasing the amount of work to update the wrapper.[2]
In 2010, the Project Phoenix began; an effort to clean up the wxPythonimplementation and in the process make it compatible with Python 3.[4] The project is a new implementation of wxPython, focused on improving speed, maintainability and extensibility. Like the previous version of wxPython, it wraps the wxWidgetsC++ toolkit and provides access to theuser interface portions of the wxWidgetsAPI.[5]
With the release of 4.0.0a1 wxPython in 2017, the Project Phoenix version became the official version.[6] wxPython 4.x is the current version being developed as of June 2022.[7]
wxPython enables Python to be used forcross-platformGUI applications requiring very little, if any, platform-specific code.
This is a simple "Hello world" module, depicting the creation of the two mainobjects in wxPython (the main window object and the application object), followed by passing the control to theevent-driven system (by callingMainLoop()) which manages the user-interactive part of the program.
#!/usr/bin/env python3importwxapp=wx.App(False)# Create a new app, don't redirect stdout/stderr to a window.frame=wx.Frame(None,title="Hello World")# A Frame is a top-level window.frame.Show(True)# Show the frame.app.MainLoop()
This is another example of the wxPython Close Button with wxPython GUI display show in Windows 10 operating system.
importwxclassWxButton(wx.Frame):def__init__(self,*args,**kw):super(WxButton,self).__init__(*args,**kw)self.InitUI()defInitUI(self):pnl=wx.Panel(self)closeButton=wx.Button(pnl,label='Close Me',pos=(20,20))closeButton.Bind(wx.EVT_BUTTON,self.OnClose)self.SetSize((350,250))self.SetTitle('Close Button')self.Centre()defOnClose(self,e):self.Close(True)defmain():app=wx.App()ex=WxButton(None)ex.Show()app.MainLoop()if__name__=="__main__":main()
Being a wrapper, wxPython uses the samefree software license used bywxWidgets (wxWindows License)[8]—which is approved byFree Software Foundation andOpen Source Initiative.
