On Wed, 15 Feb 2006 10:16:07 +, Dennis Lee Bieber wrote:
> Why bother collecting the "factors" into a list only to print them
> at the bottom of the procedure -- you aren't returning a value from
> factor(), so I'd suggest dropping the
> factors = []
> and
> print factors
>
[EMAIL PROTECTED] wrote:
> But running it in IDLE just locks up the
> computer. Bad Windows.
yeah, right - blame it all on Microsoft!
try ctrl-F6 (or Shell / Restart Shell from the menu) in IDLE, which
stops programs from infinite looping
- nas
--
http://mail.python.org/mailman/listinfo/pytho
Big help guys, thanks. There does seem to be a problem with Pythons
IDLE. If I run my oridgional program from a dos shell I can hit Ctrl-C
and free up the procesor, But running it in IDLE just locks up the
computer. Bad Windows. Thanks for the help with a more efficent
algorythm.
David KG2LI
On Tue, 14 Feb 2006 08:42:38 -0800, [EMAIL PROTECTED] wrote:
> If I un-comment any line in this program below the line where I
> commented " all OK up to this point " This program locks up my
> computer.
It locks up the operating system as well? Shame on Windows.
What happens if you type ctrl-C
On 14 Feb 2006 08:42:38 -0800 in comp.lang.python, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
>If I un-comment any line in this program below the line where I
>commented " all OK up to this point " This program locks up my
>computer.
Hmm. Ctrl-C gets me out just fine. In Idle, at least.
>
Using CPython or GMPY with a smarter algorithm in acceptable time you
can find that:
12345678987654 == 2 * 3 * 2057613164609
It's a very big number to factorize with that naive algorithm, so the
program hangs... (I have used an online factoring service).
Bye,
bearophile
--
http://mail.python.o
[EMAIL PROTECTED]
> If I un-comment any line in this program below the line where I
> commented " all OK up to this point " This program locks up my
> computer.
>
> Windows task manager will show "Not Responding" for Python in the
> Applications tab and in the Performance tabe the CPU usage will be
