hahah true. Sorry folks. I am running a third party scripting machine that uses python. It's the third-party program that is at fault. More detail involved that you don't need to know, but it's not python's "fault".
Sorry for the inconvenience. On Aug 14, 11:47 am, Fredrik Lundh <[EMAIL PROTECTED]> wrote: > korean_dave wrote: > > Still the same output... > > > Here's the actual code... > > > for x in range(0,2): > > for y in range(0,27): > > for z in range(0,15): > > print(str(x) + " " + str(y) + " " + str(z)) > > umm. that's even less related to your original output than your earlier > code sample. > > $ python actual_code.py > 0 0 0 > 0 0 1 > 0 0 2 > 0 0 3 > 0 0 4 > ... > 1 26 10 > 1 26 11 > 1 26 12 > 1 26 13 > 1 26 14 > > please do a little more debugging on your own machine before claiming > that fundamental python features that's been around for ages suddenly > won't work. > > </F> -- http://mail.python.org/mailman/listinfo/python-list
