Installer wxpython avec Homebrew

Liens du projet

• Page d'accueil
• Dépôt
• Docs amont
• Page du gestionnaire de paquets

Commandes et alias

• helpviewer
• img2png
• img2py
• img2xpm
• pycrust
• pyshell
• pyslices
• pyslicesshell
• pywxrc
• wxdemo
• wxdocs
• wxget

Historique du projet

The official history says wxPython began in 1996, after Robin Dunn discovered Python bindings while evaluating cross-platform GUI toolkits. Dunn worked with Harri Pasanen, with help from Edward Zimmerman, to advance early wxWidgets bindings into wxPython 0.2.

The first versions were maintained by hand, which became fragile as the codebase grew. In 1997 Dunn used SWIG to reimplement the bindings, and in summer 1998 the first modern wxPython release appeared for wxWidgets 2.0. The changelog still goes back to release 0.3 in 1998.

Project Phoenix later replaced Classic wxPython with a from-the-ground-up implementation focused on speed, maintainability, extensibility, Python 3 compatibility, and removing accumulated cruft. The official overview notes that Phoenix is intentionally not fully backwards compatible, though many applications can migrate with minor changes.

Historique d'adoption

wxPython became one of Python's major desktop GUI choices alongside Tkinter, PyQt/PySide, and later web-driven app shells. Its appeal was always native widgets with little platform-specific code, backed by wxWidgets rather than an emulated toolkit.

The Phoenix transition was also an adoption transition: users had to move old Classic code to Python 3-era APIs. The official docs still foreground the Migration Guide for programmers porting from Classic wxPython to Phoenix.

Modes d'utilisation

Developers import wx, create a wx.App, instantiate frames and controls, bind events, and run MainLoop. The package also includes demo, shell, resource, image-conversion, documentation, and inspection-oriented tools that make it useful as a full GUI development environment rather than just a runtime binding.

In packaging, wxPython is notable because it wraps a large C++ GUI toolkit and ships platform-specific wheels or builds tied to wxWidgets versions. The changelog records ongoing work to keep pace with Python, wxWidgets, operating-system, and build-tool changes.

Pourquoi les passionnés de paquets s'y intéressent

wxPython is package-nerd significant because it is a classic binding package: a large native-code bridge that lets a high-level language use a mature C++ toolkit. Its Classic-to-Phoenix migration is a textbook example of how language runtimes, binding generators, binary wheels, and GUI frameworks force long-lived packages to reinvent themselves.

Chronologie

• 1995: Robin Dunn discovered wxWidgets and Python while looking for a cross-platform C++ GUI toolkit.
• 1996: Official history dates the start of wxPython history to before the turn of the century, back in 1996.
• 1997: SWIG was adopted to reduce the maintenance burden of hand-written bindings.
• 1998: The first modern wxPython release appeared in summer 1998; the changelog goes back to 0.3.
• 2010s: Project Phoenix rebuilt wxPython for maintainability and Python 3.
• 2025-04-09: wxPython 4.2.3 released, built on wxWidgets 3.2.7.
• 2026-02-08: wxPython 4.2.5 released, built on wxWidgets 3.2.9.

Related projects

• wxPython is related to wxWidgets, Project Phoenix, Classic wxPython, SWIG, Tkinter, PyQt/PySide, wxGlade, wxFormBuilder, and Python desktop GUI applications.

Sources

• https://docs.wxpython.org/MigrationGuide.html
• https://github.com/wxWidgets/Phoenix
• https://wiki.wxpython.org/RobinDunn
• https://wxpython.org/pages/changes/index.html
• https://wxpython.org/pages/history/
• https://wxpython.org/pages/overview/index.html