On Monday, April 1, 2013 8:33:47 AM UTC+10:30, Eric Parry wrote: > On Sunday, March 31, 2013 9:45:36 AM UTC+10:30, Dave Angel wrote: > > > On 03/30/2013 06:06 PM, Eric Parry wrote: > > > > > > > On Saturday, March 30, 2013 8:41:08 AM UTC+10:30, Dave Angel wrote: > > > > > > >> On 03/29/2013 05:47 PM, Eric Parry wrote: > > > > > > >> > > > > > > >>> <SNIP> > > > > > > >> > > > > > > >> Sometimes a bug in such a function will cause it to run indefinitely, > > > > > > >> > > > > > > >> and/or to overflow the stack. I don't see such a bug in this function. > > > > > > >> > > > > > > >> > > > > > > >> > > > > > > >> > > > > > > >> > > > > > > >> -- > > > > > > >> > > > > > > >> DaveA > > > > > > > > > > > > > > The exit() did not work. > > > > > > > > > > > > Would you like to elaborate? exit() is supposed to take an int > > > > > > parameter, but the author apparently didn't notice that. So perhaps you > > > > > > got an exception of some sort. Change it to exit() or exit(0) and it > > > > > > might solve the problem, depending on what the problem was. > > > > > > > > > > > > > I replaced it with return = 0, and that does work. > > > > > > > > > > > > No it doesn't. return = 0 is a syntax error in both Python 2.x and 3.x > > > > > > > > > > > > But if you changed it to a valid return statement, then that's why it > > > > > > doesn't stop on the first solution. > > > > > > > > > > > > > > > > > > -- > > > > > > DaveA > > > > I think in the original it was exit(a). That did not work either. > > I'll try the others. > > Eric.
I tried all those things. The program keeps running after the solution in every case. Never mind. It won't do that in VBA when I finish it. Eric. -- http://mail.python.org/mailman/listinfo/python-list
