I have run the 'testall' instead of 'autotest' and that seems to work
a little better.. I can at leat find out where in the tests it is dieing..
here are the results...
test_grammar
1. Parser
1.1 Tokens
1.1.1 Backslashes
1.1.2 Numeric literals
1.1.2.1 Plain integers
1.1.2.2 Long integers
1.1.2.3 Floating point
1.1.3 String literals
1.2 Grammar
single_input
file_input
expr_input
eval_input
funcdef
simple_stmt
expr_stmt
1
(1, 2, 3)
print_stmt
1 2 3
1 2 3
1 1 1
pass_stmt
flow_stmt
break_stmt
continue_stmt
return_stmt
raise_stmt
import_stmt
[1]
[2]
[3]
[4]
[5]
global_stmt
exec_stmt
if_stmt
while_stmt
for_stmt
[1]
[2]
[3]
try_stmt
suite
test
comparison
binary mask ops
shift ops
additive ops
multiplicative ops
unary ops
selectors
atoms
classdef
test_opcodes
2. Opcodes
XXX Not yet fully implemented
2.1 try inside for loop
test_operations
3. Operations
XXX Not yet implemented
test_builtin
4. Built-in functions
test_b1
abs
apply
chr
cmp
coerce
print_error called but no exception
IOT/Abort trap(coredump)
--Lance Ellinghouse lance@markv.com UNIX Systems Support support@markv.com Mark V Systems Limited Voice: +1 818 995 7671 FAX: +1 818 995 4267