kmonsoor / pyglet

Automatically exported from code.google.com/p/pyglet
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

"ImportError: No module named future" in image.MATRIX_RGB test suite. #729

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Have you tried Pyglet 1.2 alpha1 or the repository code?
default branch, changeset: 
https://code.google.com/p/pyglet/source/detail?r=9781eb46dca2, Thu Apr 03 
19:13:36 2014 +0100
using Python 2.7.6

What steps will reproduce the problem?
1. complete tests/test.py
2. read the pyglet.%d.log

Paste in the traceback or error message:
ERROR Cannot load test for image.MATRIX_RGB
Traceback (most recent call last):
  File "tests/test.py", line 265, in test
    module = self.get_module(options.test_root)
  File "tests/test.py", line 243, in get_module
    module = __import__(name)
  File "tests/../tests/image/MATRIX_RGB.py", line 10, in <module>
    from future import print_function
ImportError: No module named future
INFO --- test (34/45) image.MATRIX_RGBA
ERROR Cannot load test for image.MATRIX_RGBA
Traceback (most recent call last):
  File "tests/test.py", line 265, in test
    module = self.get_module(options.test_root)
  File "tests/test.py", line 243, in get_module
    module = __import__(name)
  File "tests/../tests/image/MATRIX_RGBA.py", line 10, in <module>
    from future import print_function
ImportError: No module named future

Problem:
https://code.google.com/p/pyglet/source/detail?r=1d7499251e0e
`from future import print_function` <- should be __future__.

Proposed fix: from_future_fix.patch

Also, inconsistent use of print statement/statement with brackets/function in 
different parts of the code may be confusing.
Like in "tests/test.py" lines 585, 600. print statement is used as it was a 
function:
`print('Test results are saved in log file:', options.log_file)`

Proposed fix: use_print_func_in_test.patch

Original issue reported on code.google.com by Risimi...@gmail.com on 5 Apr 2014 at 12:52

Attachments:

GoogleCodeExporter commented 9 years ago
My fault, sorry.

Original comment by ccanepacc@gmail.com on 6 Apr 2014 at 6:36

GoogleCodeExporter commented 9 years ago
This issue was closed by revision 511763701504.

Original comment by useboxnet on 17 Apr 2014 at 6:50