Re: About reading Python code

2008-03-25 Thread Phil
On 2008-03-18, sturlamolden <[EMAIL PROTECTED]> wrote: > First, I recommend that you write readable code! Don't use Python as > if you're entering the obfuscated C contest. > > Two particularly important points: > > * Comments are always helpful to the reader. It would be nice if this was the case

Re: About reading Python code

2008-03-18 Thread sturlamolden
On 18 Mar, 08:00, hellt <[EMAIL PROTECTED]> wrote: > under Microsoft Visual Studio do you mean IronPython instance? AFAIK, with the latest VS 2008 you can develop for CPython and IronPython. http://blogs.msdn.com/haibo_luo/archive/2007/10/16/5482940.aspx -- http://mail.python.org/mailman/lis

Re: About reading Python code

2008-03-18 Thread hellt
On 18 мар, 03:57, sturlamolden <[EMAIL PROTECTED]> wrote: > On 17 Mar, 04:54, WaterWalk <[EMAIL PROTECTED]> wrote: > > > So I'm curious how to read code effectively. I agree that python code > > is clear, but when it becomes long, reading it can still be a hard > > work. > > First, I recommend that

Re: About reading Python code

2008-03-17 Thread Jeff Schwab
sturlamolden wrote: > On 17 Mar, 04:54, WaterWalk <[EMAIL PROTECTED]> wrote: > >> So I'm curious how to read code effectively. I agree that python code >> is clear, but when it becomes long, reading it can still be a hard >> work. > > First, I recommend that you write readable code! Don't use Pyt

Re: About reading Python code

2008-03-17 Thread Paul Rubin
WaterWalk <[EMAIL PROTECTED]> writes: > from one function to another. But with Python, the debugger is a > little primitive. The default IDLE doesn't even allow me to set a > breakpoint. When the code is long, I am often lost in it. Try winpdb.org which despite the name has nothing to do with MS W

Re: About reading Python code

2008-03-17 Thread sturlamolden
On 17 Mar, 04:54, WaterWalk <[EMAIL PROTECTED]> wrote: > So I'm curious how to read code effectively. I agree that python code > is clear, but when it becomes long, reading it can still be a hard > work. First, I recommend that you write readable code! Don't use Python as if you're entering the o

Re: About reading Python code

2008-03-17 Thread Gabriel Genellina
En Mon, 17 Mar 2008 01:54:01 -0200, WaterWalk <[EMAIL PROTECTED]> escribi�: > Hello. I wonder what's the effective way of figuring out how a piece > of python code works. With C I often find it very useful to be able to > run the code in step mode and set breakpoints in a debugger so I can > wat

Re: About reading Python code

2008-03-17 Thread Roman Dodin
WaterWalk пишет: > Hello. I wonder what's the effective way of figuring out how a piece > of python code works. With C I often find it very useful to be able to > run the code in step mode and set breakpoints in a debugger so I can > watch how the it executes, how the data change and how the code

Re: About reading Python code

2008-03-17 Thread Nir
On Mar 17, 5:54 am, WaterWalk <[EMAIL PROTECTED]> wrote: > Hello. I wonder what's the effective way of figuring out how a piece > ofpythoncode works. With C I often find it very useful to be able to > run the code in step mode and set breakpoints in adebuggerso I can > watch how the it executes, ho

Re: About reading Python code

2008-03-17 Thread Ben C
On 2008-03-17, WaterWalk <[EMAIL PROTECTED]> wrote: > Hello. I wonder what's the effective way of figuring out how a piece > of python code works. With C I often find it very useful to be able to > run the code in step mode and set breakpoints in a debugger so I can > watch how the it executes, how

Re: About reading Python code

2008-03-17 Thread WaterWalk
On Mar 17, 1:54 pm, Stargaming <[EMAIL PROTECTED]> wrote: > On Sun, 16 Mar 2008 20:54:01 -0700, WaterWalk wrote: > > Hello. I wonder what's the effective way of figuring out how a piece of > > python code works. > > If your Python code is well-written, it should be easy figuring out what > it means

Re: About reading Python code

2008-03-16 Thread Stargaming
On Sun, 16 Mar 2008 20:54:01 -0700, WaterWalk wrote: > Hello. I wonder what's the effective way of figuring out how a piece of > python code works. If your Python code is well-written, it should be easy figuring out what it means by just reading it. For more complex programs, of course, this me

Re: About reading Python code

2008-03-16 Thread WaterWalk
On Mar 17, 11:54 am, WaterWalk <[EMAIL PROTECTED]> wrote: > Hello. I wonder what's the effective way of figuring out how a piece > of python code works. With C I often find it very useful to be able to > run the code in step mode and set breakpoints in a debugger so I can > watch how the it execute

About reading Python code

2008-03-16 Thread WaterWalk
Hello. I wonder what's the effective way of figuring out how a piece of python code works. With C I often find it very useful to be able to run the code in step mode and set breakpoints in a debugger so I can watch how the it executes, how the data change and how the code jumps from one function to