Guilherme Polo wrote:
> there is a
> gui designer tool for tkinter called GUI Designer (what a bad name),
> which used to be called SpecTcl, where you can design the menus and it
> then converts to python code.
I tried it. after about 10 minutes I was as far as "help not found."
Is anyone out t
[EMAIL PROTECTED] wrote:
> menudef = """
> File
> New,callNew,Ctrl-N
> New Window, callNewWindow, Ctrl-Shift-N
> __
> Open, lambda e=0:para(1), Ctrl-O
Nice design. I looked at it for a few seconds and didn't even
think about pressing F1.
Mine does
I'm writing Python as if it were strongly typed, never recycling a
name to hold a type other than the original type.
Is this good software engineering practice, or am I missing something
Pythonic?
--
http://mail.python.org/mailman/listinfo/python-list
By convention, I've read, your module begins with its import
statements. Is this always sensible?
I put imports that are needed for testing in the test code at the end
of the module. If only a bit of the module has a visual interface, why
pollute the global namespace with 'from Tkinter import *'?
Thanks, all.
Good to know no one's been beheaded.
Yes to separating test and non-test code, but no if that will just
turn one modest module into two modules, smaller still.
Amen to 'practicality beats purity.'
Do wish we had a good, thorough convention set. I wrote one for Java.
It took a lot o
I assembled a good conventions set for Java. View it at
http://www.martinrinehart.com/articles/code-conventions.html (is that
better, Steve?)
It followed a logical organization; it was built from four other
extensive (if not well-organized) convention sets and it scrupulously
avoided injecting my
Daniel Fetchinson wrote:
> I'm sorry to disappoint you but this project has already been completed:
>
> http://www.python.org/dev/peps/pep-0008/
Daniel, PEP 8 is anything but complete. How much of the following
simple question can you answer from there:
Given that you can name things with Upper
101 - 107 of 107 matches
Mail list logo