Ok, I now understand the role of wx. I'm going to un-install wx. I want
to keep this program as close to the original as I can, which means I
will use Tkinter from here on out. GUIs of different sorts seem to be
a burgeoning industry.
I'm willing to give vim a shot. I believe in an earlier thread
unrelated to this, Alan suggested it. I'm perhaps incorrectly assuming
vim will take care of the Tkinter problem. If these editors aren't
really the source of some the error reporting problem, then I'm going
to have to come up with new thinking or some tactic that will get to
the real errors. If there is an influence of the editors, then I would
think it has something to do with the interface to Python, so it comes
down to which editor has the best or most stable interface with
Python. When Alan suggested it, there was something about the apparent
awkwardness of executing the code, which made me pass on it. I'm going
back to find out what that was.
Yep, I missed this in your other post:
"In particular you want this section: http://www.voidspace.org.uk/python/validate.html#the-standard-functions"
Marc Tompkins wrote:
On Thu, Feb 19, 2009 at 9:58 AM, Wayne
Watson <sierra_mtnv...@sbcglobal.net>
wrote:
I now have wxPython, IDLE and
Vim installed. IDLE didn't disappear
during the wx install. It looks as though wxPython re-compiled library
files. I'll be exploring vim now.
wxPython doesn't replace or remove anything - I still have IDLE on my
machine, I just don't use it. The wxPython installer wasn't
re-compiling Python - it was using Python to compile its own scripts
for use on your machine.
Once again, to be clear: wxPython is an alternative to Tkinter, not to
IDLE - it's a different toolkit for creating GUI applications.
The upsides:
- it's a good deal more sophisticated and powerful (I feel) than
Tkinter, and the apps you produce using it will look a lot more
"native" (on Windows, they'll look like Windows apps; on OS X they'll
have the Apple look and feel, etc.) and therefore more
professional/less hobbyist-like.
- the syntax of working with wxPython widgets feels more Pythonic (to
me). It's a matter of personal taste, but I tried Tkinter for a few
days and hated it; I tried wxPython and got hooked.
The downsides:
- it's not part of Python proper, so it's an extra dependency
(although there's a great install-package creator called Gui2Exe that
will bundle your program along with Python and all other dependencies
into a Windows-style installer, so you can distribute just one file to
your potential users.)
- it's not part of Python proper, so most tutorials/Python books
barely mention its existence. There's (1) excellent book, "wxPython in
Action", a couple of very active mailing lists, an excellent and
gigantic demo program with sample code for almost every widget, and
Google. Other than that, you're on your own.
--
www.fsrtechnologies.com
_______________________________________________
Tutor maillist - Tutor@python.org
http://mail.python.org/mailman/listinfo/tutor
--
Wayne Watson (Watson Adventures, Prop., Nevada City, CA)
(121.01 Deg. W, 39.26 Deg. N) GMT-8 hr std. time)
"Nature, to be commanded, must be obeyed."
-- Sir Francis Bacon
Web Page: <www.speckledwithstars.net/>
|
