Kosta, just FYI, your emails continue to look very rough on this end:
Not really keen on this change; its not as intuitive to me as the original.
It's really not reasonable to install something ending in .py into $PATH, IMHO. Further, renaming on install doesn't seem like the right thing to do either (and it'd be very unconventional).
Right now, chirpw becomes the installed binary for the windowed version. We can't really use "chirp" unless we put it in a different directory, as it conflicts with the package name. IMHO, chirpc is a reasonable alternative. I don't think it's likely to be confused as a compiler to anyone other than java folk. The other option in my mind would be "chirpcli", but then it would be different from "chirpw" and I'm really not in favor of renaming that to "chirpwindowed" :)
--Dan