wxPython is not suitable for inclusion for many reasons. One reason is that it is a *huge* library which requires a lot of constant work (bugfixing, documentation, lots of commits, etc...) which cannot weight on python development. Keeping the two worlds separated is better for both of them, especially for wxPython which doesn't have to follow the strict politics surrounding the python stdlib. For example, wxPython is free to break some API backward compatibility on every new major version if this is desired. Such a thing couldn't happen if it were in the stdlib for obvious reasons.
--- Giampaolo http://code.google.com/p/pyftpdlib/ http://code.google.com/p/psutil/ 2011/1/26 Brendan Simon (eTRIX) <brendan.si...@etrix.com.au>: > Since it seems the python motto is "Batteries included", then it would seem > to me that wxPython is the natural fit as it also has "Batteries included" > (e.g. accessibility, native look-n-feel, mature and evolving, can produce > simple or complex gui programs, etc, etc). > > -- > Brendan Simon > www.etrix.com.au > > -- > http://mail.python.org/mailman/listinfo/python-list > -- http://mail.python.org/mailman/listinfo/python-list
