gdkar / pyglet

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

just release 1.2 already #730

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Have you tried Pyglet 1.2 alpha1 or the repository code?

Yes, that's the problem.  1.2 seems to work okay.

Please put 1.2 on PyPI; it's been languishing forever and it's the only gaming 
library which even has a hope of just working normally via Pip.

What steps will reproduce the problem?
1. "pip install pyglet" on OS X
2. try to follow the tutorial
3. it tracebacks horribly
4. a user with less intimate knowledge of how to screw around with python 
packaging would not have figured out how to proceed

Paste in the traceback or error message:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File ".../site-packages/pyglet/window/__init__.py", line 1669, in <module>
    from pyglet.window.carbon import CarbonPlatform, CarbonWindow
  File ".../site-packages/pyglet/window/carbon/__init__.py", line 69, in <module>
    framework='/System/Library/Frameworks/QuickTime.framework')
  File ".../site-packages/pyglet/lib.py", line 90, in load_library
    return self.load_framework(kwargs['framework'])
  File ".../site-packages/pyglet/lib.py", line 226, in load_framework
    lib = ctypes.cdll.LoadLibrary(realpath)
  File ".../ctypes/__init__.py", line 443, in LoadLibrary
    return self._dlltype(name)
  File ".../ctypes/__init__.py", line 365, in __init__
    self._handle = _dlopen(self._name, mode)
OSError: dlopen(/System/Library/Frameworks/QuickTime.framework/QuickTime, 6): 
no suitable image found.  Did find:
    /System/Library/Frameworks/QuickTime.framework/QuickTime: mach-o, but wrong architecture
    /System/Library/Frameworks/QuickTime.framework/QuickTime: mach-o, but wrong architecture

Paste in the output of `python -m pyglet.info`:

Traceback (most recent call last):
  File "/Users/glyph/.virtualenvs/crappyglet/lib/python2.7/site-packages/pyglet/info.py", line 173, in _try_dump
    func()
  File "/Users/glyph/.virtualenvs/crappyglet/lib/python2.7/site-packages/pyglet/info.py", line 77, in dump_window
    import pyglet.window
  File "/Users/glyph/.virtualenvs/crappyglet/lib/python2.7/site-packages/pyglet/window/__init__.py", line 1669, in <module>
    from pyglet.window.carbon import CarbonPlatform, CarbonWindow
  File "/Users/glyph/.virtualenvs/crappyglet/lib/python2.7/site-packages/pyglet/window/carbon/__init__.py", line 69, in <module>
    framework='/System/Library/Frameworks/QuickTime.framework')
  File "/Users/glyph/.virtualenvs/crappyglet/lib/python2.7/site-packages/pyglet/lib.py", line 90, in load_library
    return self.load_framework(kwargs['framework'])
  File "/Users/glyph/.virtualenvs/crappyglet/lib/python2.7/site-packages/pyglet/lib.py", line 226, in load_framework
    lib = ctypes.cdll.LoadLibrary(realpath)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ctypes/__init__.py", line 443, in LoadLibrary
    return self._dlltype(name)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ctypes/__init__.py", line 365, in __init__
    self._handle = _dlopen(self._name, mode)
OSError: dlopen(/System/Library/Frameworks/QuickTime.framework/QuickTime, 6): 
no suitable image found.  Did find:
    /System/Library/Frameworks/QuickTime.framework/QuickTime: mach-o, but wrong architecture
    /System/Library/Frameworks/QuickTime.framework/QuickTime: mach-o, but wrong architecture
/Users/glyph/.virtualenvs/crappyglet/lib/python2.7/site-packages/pyglet/gl/gl_in
fo.py:134: UserWarning: No GL context created yet.
  warnings.warn('No GL context created yet.')
/Users/glyph/.virtualenvs/crappyglet/lib/python2.7/site-packages/pyglet/gl/gl_in
fo.py:175: UserWarning: No GL context created yet.
  warnings.warn('No GL context created yet.')
/Users/glyph/.virtualenvs/crappyglet/lib/python2.7/site-packages/pyglet/gl/gl_in
fo.py:166: UserWarning: No GL context created yet.
  warnings.warn('No GL context created yet.')
/Users/glyph/.virtualenvs/crappyglet/lib/python2.7/site-packages/pyglet/gl/gl_in
fo.py:124: UserWarning: No GL context created yet.
  warnings.warn('No GL context created yet.')
/Users/glyph/.virtualenvs/crappyglet/lib/python2.7/site-packages/pyglet/gl/glu_i
nfo.py:124: UserWarning: No GL context created yet.
  warnings.warn('No GL context created yet.')
/Users/glyph/.virtualenvs/crappyglet/lib/python2.7/site-packages/pyglet/gl/glu_i
nfo.py:149: UserWarning: No GL context created yet.
  warnings.warn('No GL context created yet.')
Python
------------------------------------------------------------------------------
sys.version: 2.7.5 (default, Aug 25 2013, 00:04:04) 
[GCC 4.2.1 Compatible Apple LLVM 5.0 (clang-500.0.68)]
sys.platform: darwin
os.getcwd(): /Users/glyph

pyglet
------------------------------------------------------------------------------
pyglet.version: 1.1.4
pyglet.__file__: 
/Users/glyph/.virtualenvs/crappyglet/lib/python2.7/site-packages/pyglet/__init__
.pyc
pyglet.options['debug_trace_depth'] = 1
pyglet.options['font'] = ('gdiplus', 'win32')
pyglet.options['xsync'] = True
pyglet.options['debug_trace_flush'] = True
pyglet.options['debug_win32'] = False
pyglet.options['debug_gl_trace'] = False
pyglet.options['debug_x11'] = False
pyglet.options['shadow_window'] = True
pyglet.options['debug_font'] = False
pyglet.options['debug_media'] = False
pyglet.options['debug_trace'] = False
pyglet.options['debug_lib'] = False
pyglet.options['graphics_vbo'] = True
pyglet.options['vsync'] = None
pyglet.options['debug_trace_args'] = False
pyglet.options['debug_gl'] = True
pyglet.options['debug_graphics_batch'] = False
pyglet.options['audio'] = ('directsound', 'openal', 'alsa', 'silent')
pyglet.options['debug_texture'] = False
pyglet.options['debug_gl_trace_args'] = False

pyglet.window
------------------------------------------------------------------------------

pyglet.gl.gl_info
------------------------------------------------------------------------------
gl_info.get_version(): 0.0.0
gl_info.get_vendor(): 
gl_info.get_renderer(): 
gl_info.get_extensions():

pyglet.gl.glu_info
------------------------------------------------------------------------------
glu_info.get_version(): 0.0.0
glu_info.get_extensions():

pyglet.gl.glx_info
------------------------------------------------------------------------------
GLX not available.

pyglet.media
------------------------------------------------------------------------------
driver: pyglet.media.drivers.openal

pyglet.media.avbin
------------------------------------------------------------------------------
AVbin not available.

pyglet.media.drivers.openal
------------------------------------------------------------------------------
Library: <CDLL '/System/Library/Frameworks/OpenAL.framework/OpenAL', handle 
7f9619caba40 at 10f8539d0>
Version: (1, 1)
Extensions:
   ALC_EXT_CAPTURE
   ALC_ENUMERATION_EXT
   ALC_EXT_MAC_OSX
   ALC_EXT_ASA
   ALC_EXT_ASA_DISTORTION
   ALC_EXT_ASA_ROGER_BEEP

Any additional info (platform/language/hardware) that may be relevant?

Original issue reported on code.google.com by Glyph.Lefkowitz on 7 Apr 2014 at 9:32

GoogleCodeExporter commented 9 years ago
I agree strongly on this. As I've posted on another issue ( 
https://code.google.com/p/pyglet/issues/detail?id=713 ), I feel like this 
project is going nowhere, even though it had and still has a lot of potential. 
I started with Python in March 2012, specifically because I wanted to write 
games. Nowadays I earn my living with Python + Django, but still look out for 
good game libraries.

I remember choosing between Pygame and Pyglet, and settled on Pygame back then 
because it seemed more mature, although I thought Pyglet to be cleaner, more 
pythonic and having more potential. However, in those past two years, there 
have been exactly 0 releases. In my opinion, by observing this project for some 
time (with some big gaps), some drastic measures need to be taken, including 
moving to Github, drastically increasing the release rate, and advertising it 
more as one of the few good libraries out there to write games with in Python 
(unfortunately there are too few of these, that's why I'm still keeping an eye 
on Pyglet).

Original comment by gwildorsok on 9 Apr 2014 at 2:09

GoogleCodeExporter commented 9 years ago
gwildorsok: are you volunteering? There are over 147 issues in the bug tracker 
(it's not accurate because some of them seem to be corrupt), and some of them 
could use some help.

That's one side of the history; although it's true that pyglet 1.2 is getting 
better and almost ready for a beta release, there are some parts that are just 
not finished. A good start point could be grepping for "TODO" in pyglet's 
source. There are also a couple of tickets related to documentation that need 
to be addressed before a release (eg, migrating from 1.1 to 1.2).

We tried to make 1.2 easier to use (you can install the latest repo code with 
pip, see: http://pyglet.org/download.html), but it needs work to be "stable".

Please don't take offence because I close this ticket as invalid. This kind of 
conversation should happen on the mailing list.

Original comment by useboxnet on 12 Apr 2014 at 1:24