Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AttributeError: 'module' object has no attribute 'getoutput' #86

Closed
r58Playz opened this issue Mar 27, 2019 · 3 comments
Closed

AttributeError: 'module' object has no attribute 'getoutput' #86

r58Playz opened this issue Mar 27, 2019 · 3 comments

Comments

@r58Playz
Copy link

AttributeError: 'module' object has no attribute 'getoutput'

@r58Playz
Copy link
Author

r58Playz commented Apr 2, 2019

Traceback (most recent call last):
File "main.py", line 18, in
from pyglet.gl import *
File "C:\Python27\lib\site-packages\pyglet\gl_init_.py", line 239, in
import pyglet.window
File "C:\Python27\lib\site-packages\pyglet\window_init_.py", line 1896, in
gl.create_shadow_window()
File "C:\Python27\lib\site-packages\pyglet\gl_init
.py", line 208, in create_shadow_window
shadow_window = Window(width=1, height=1, visible=False)
File "C:\Python27\lib\site-packages\pyglet\window\win32_init
.py", line 134, in init
super(Win32Window, self).init(*args, **kwargs)
File "C:\Python27\lib\site-packages\pyglet\window_init
.py", line 501, in init
display = get_platform().get_default_display()
File "C:\Python27\lib\site-packages\pyglet\window_init_.py", line 1845, in get_default_display
return pyglet.canvas.get_display()
File "C:\Python27\lib\site-packages\pyglet\canvas_init_.py", line 77, in get_display
from pyglet.app import displays
File "C:\Python27\lib\site-packages\pyglet\app_init_.py", line 154, in
from pyglet.app.base import EventLoop
File "C:\Python27\lib\site-packages\pyglet\app\base.py", line 4, in
standard_library.install_aliases()
File "C:\Python27\lib\site-packages\future\standard_library_init_.py", line 459, in install_aliases
import(oldmodname)
File "C:\Users\toshi\Minecraft-master\Minecraft-master\commands.py", line 12, in
from blocks import BlockID
File "C:\Users\toshi\Minecraft-master\Minecraft-master\blocks.py", line 17, in
from utils import load_image, make_nbt_from_dict, extract_nbt
File "C:\Users\toshi\Minecraft-master\Minecraft-master\utils.py", line 12, in
import globals as G
File "C:\Users\toshi\Minecraft-master\Minecraft-master\globals.py", line 20, in
from pyglet.resource import get_settings_path
File "C:\Python27\lib\site-packages\pyglet\resource.py", line 88, in
standard_library.install_aliases()
File "C:\Python27\lib\site-packages\future\standard_library_init_.py", line 462, in install_aliases
obj = getattr(oldmod, oldobjname)
AttributeError: 'module' object has no attribute 'getoutput'

@Nebual Nebual closed this as completed in 6ed4b70 Apr 6, 2019
Nebual added a commit that referenced this issue Apr 6, 2019
@Nebual
Copy link
Collaborator

Nebual commented Apr 6, 2019

Hmm, amusing how errors can grow in stale projects purely from the passage of time...

As python2.7 enters its final hours, it seems the futures library has started backporting many of Python3's features back to Python2.7 to ease the transition, including renaming several methods from the deprecated 2.7 https://docs.python.org/2/library/commands.html module to follow their Python3 naming conventions. Pyglet uses part of futures, and we use Pyglet. We had a module named commands.py which conflicted with the official one - a simple rename has allowed this ancient project to boot again, though I wouldn't be surprised if it needed more updating.

I'm slightly tempted to rewrite it in Python3, assuming all the dependencies have Python3 equivalents...

@r58Playz
Copy link
Author

True. You should rewrite it, to keep the project running.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants