Temperament finder bug

I was looking for really accurate 31-limit EDOs, so I started at the
most obvious choice possible: 23-EDO. Unfortunately, it was so obvious
it caused the temperament finder to explode. Here's what I get:

http://x31eq.com/cgi-bin/rt.cgi?ets=23&limit=31

didn't work

Traceback (most recent call last):
File "/home/public/cgi-bin/rt.cgi", line 96, in <module>
printAll([], etNames, plimit, numbers, warts)
File "/home/public/cgi-bin/rt.cgi", line 11, in printAll
newets = et.NamedETs(names[0], plimit, warts)
File "/home/public/cgi-bin/et.py", line 346, in NamedETs
for poss in alternativeMappings(prime, resource)
File "/home/public/cgi-bin/et.py", line 548, in alternativeMappings
result = alternativeMappings(et, resource, index+1)
File "/home/public/cgi-bin/et.py", line 560, in alternativeMappings
EqualTemperament(mapping, et.primes), resource, index+1)
File "/home/public/cgi-bin/et.py", line 560, in alternativeMappings
EqualTemperament(mapping, et.primes), resource, index+1)
File "/home/public/cgi-bin/et.py", line 560, in alternativeMappings
EqualTemperament(mapping, et.primes), resource, index+1)
File "/home/public/cgi-bin/et.py", line 560, in alternativeMappings
EqualTemperament(mapping, et.primes), resource, index+1)
File "/home/public/cgi-bin/et.py", line 560, in alternativeMappings
EqualTemperament(mapping, et.primes), resource, index+1)
File "/home/public/cgi-bin/et.py", line 548, in alternativeMappings
result = alternativeMappings(et, resource, index+1)
File "/home/public/cgi-bin/et.py", line 548, in alternativeMappings
result = alternativeMappings(et, resource, index+1)
File "/home/public/cgi-bin/et.py", line 560, in alternativeMappings
EqualTemperament(mapping, et.primes), resource, index+1)
File "/home/public/cgi-bin/et.py", line 548, in alternativeMappings
result = alternativeMappings(et, resource, index+1)
File "/home/public/cgi-bin/et.py", line 544, in alternativeMappings
resource.consume()
File "/home/public/cgi-bin/et.py", line 596, in consume
raise ResourceExhausted, "Set number of calls exceeded"
ResourceExhausted: Set number of calls exceeded

-----

Too much error to handle?

-Mike

--- In tuning@yahoogroups.com, Mike Battaglia <battaglia01@...> wrote:

> Too much error to handle?

I blame it on you, for doing such a weird thing in the first place. However, it can handle 23 in the 23-limit, and 31 in the 31-limit, which seems fair.