Thanks for looking ;-)
I used python 3.2 's 2to3.py ;-)
in a console eval(input('prompt text')) gives no error
I solved (workaround) it by just put that part after a # ...
and gave a fake result directly ...
Now a lot of tests run but with a lot of failures ;-) ...
=========================================
two examples
ERROR Failure in graphics.RETAINED_INDEXED
ERROR Traceback (most recent call last):
File "tests\..\tests\graphics\RETAINED_INDEXED.py", line 64, in
test_v3f_c4f
self.generic_test('v3f', v3f_data, 'c4f', c4f_data)
File "tests\..\tests\graphics\RETAINED_INDEXED.py", line 42, in
generic_test
self.check(get_ordered_data(v_data, n_v), vertices, n_v)
File "tests\..\tests\graphics\RETAINED_INDEXED.py", line 25, in check
(e, r))
AssertionError: Feedback array is in error: 0.7279411764705882,
0.24267578125
ERROR Failure in graphics.RETAINED
ERROR Traceback (most recent call last):
File "tests\..\tests\graphics\RETAINED.py", line 70, in test_v3f_c4f_t4f
self.generic_test('v3f', v3f_data, 'c4f', c4f_data, 't4f', t4f_data)
File "tests\..\tests\graphics\RETAINED.py", line 36, in generic_test
self.check(v_data, vertices, n_v)
File "tests\..\tests\graphics\RETAINED.py", line 20, in check
(e, r))
AssertionError: Feedback array is in error: 0.0, 0.0439453125
==================================================
Yes probably my NVIDIA is too old??
2012/7/16 Andreas Schiefer <[email protected]>
> On Sun, Jul 15, 2012 at 5:03 PM, PKHG <[email protected]> wrote:
> > ERROR Failure in app.EVENT_LOOP
> [...]
> > AssertionError: 1.0073020453716888 != 1 within 2 places
> >
> > though I think the difference is very small ;-) so I suppose the
> > assertion commands should be adjusted a bit?
>
> I do not see these errors on Win7 64 bit with Python 3.2. But as the
> errors seem very small, I think you can ignore them.
>
>
>
> > ERROR Failure in graphics.IMMEDIATE
> [...]
> > AssertionError: Feedback array is in error: 0.0, 0.0439453125
>
> This kind of error is most probably due to the Nvidia driver (which I
> guess you are using). There should be even a warning or note about
> that in the test output (not in the log file unfortunately). You can
> safely ignore these errors.
>
>
> > Running Test: window.WINDOW_OPEN (9/135)
> [...]
> > File "tests\test.py", line 280, in test
> > eval(input('Press return to begin test...'))
> > File "<string>", line 1
> >
> > ^
> > SyntaxError: unexpected EOF while parsing
>
> This one is strange, have you tried running just this single test
> (instead of the whole test suite)?
> You can start it with: "python tests/test.py window.WINDOW_OPEN"
>
> Also, I do not have a "eval(...)" at line 280 in test.py, where the
> error occurs. Was this added during the conversion with 2to3? If so,
> which version of 2to3 were you using? I used the one from Python 3.2,
> and it does not introduce a call to eval() at this line.
>
>
> Andy
>
> --
> You received this message because you are subscribed to the Google Groups
> "pyglet-users" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/pyglet-users?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"pyglet-users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pyglet-users?hl=en.
