Tk vs wxPython ?

[Robin Munn]

Gerrit Holl <gerrit at nl.linux.org> wrote:
>=?ISO-8859-1?Q? Aur=E9lien?= =?ISO-8859-1?Q?G=E9ron ?= schreef op woensdag  4 juni om 19:12:28 +0000:
>> I'm new here, so maybe this is a debate that has been going on already.  If
>> that's the case, please ignore this post...
>> 
>> ** Why isn't Python shipped with wxPython instead of Tk ? **
> 
> This has been very extensively discussed in the past. Without any
> satisfactory (to me at least) conclusion though, because Python
> is still shipped with Tk ;). This one, I think the first long one
> and the most comprehensive, contains a lot of information:
> 
> http://www.google.nl/groups?hl=nl&lr=&ie=UTF-8&oe=UTF-8&threadm=00001667%40bossar.com.pl&rnum=3&prev=/groups%3Fas_q%3DTkinter%2520WxPython%26ie%3DUTF-8%26oe%3DUTF-8%26as_ugroup%3Dcomp.lang.python%26as_uauthors%3DGerrit%2520Holl%26lr%3D%26hl%3Dnl
> 
> I am certainly not going to ignore your post, however.
> 
>> Any comments on this ? Anyone else want to vote ?
> 
> Maybe we - being the people wanting to move to WxPython - should write a PEP...

Although I would very much like to see wxPython become an accepted part
of the standard library, I shudder to think of the flamewar that would
result from discussion of such a PEP. If you thought the ternary
operator discussion was bad, "you ain't seen nothin' yet, pardner"! :-)

Well, given that this is c.l.py, it would probably be a friendly
flamewar for the most part, but a flamewar it would be.

That doesn't mean a PEP shouldn't be written; it does mean that I, for
one, am *not* volunteering to write it. :-)

-- 
Robin Munn <rmunn at pobox.com>
http://www.rmunn.com/
PGP key ID: 0x6AFB6838    50FF 2478 CFFB 081A 8338  54F7 845D ACFD 6AFB 6838