1) I'm actually using Python 3.3.0rc1 at the moment.

2) The "PY3K" file says that 2to3 is supposed to be run automatically when
you run "python setup.py install" -- but it doesn't.  Not to worry, "2to3
-w pyglet" did the trick.

3) One error was output during "sudo python3 setup.py install":

[snip]
byte-compiling
/Library/Frameworks/Python.framework/Versions/3.3/lib/python3.3/site-packages/pyglet/text/formats/html.py
to html.cpython-33.pyc
  File
"/Library/Frameworks/Python.framework/Versions/3.3/lib/python3.3/site-packages/pyglet/text/formats/html.py",
line 54
    from . import html.parser
                      ^
SyntaxError: invalid syntax

byte-compiling
/Library/Frameworks/Python.framework/Versions/3.3/lib/python3.3/site-packages/pyglet/text/formats/structured.py
to structured.cpython-33.pyc
[snip]


4) The buggy non-visible-window behavior is _exactly_ the same as far as I
can tell.  Where's a Cocoa expert when you need one?

~ Nathan




On Sat, Sep 15, 2012 at 5:13 PM, Nathan <[email protected]> wrote:

> On Sat, Sep 15, 2012 at 4:09 PM, Phillip Nguyen <[email protected]>wrote:
>
>>
>> I've committed some code changes to make pyglet's cocoa backend
>> compatible with Python 3.2.  Mostly a lot of unicode vs bytes issues that
>> needed to be fixed when interfacing the objc runtime via ctypes.  Pyglet
>> still needs to be converted with 2to3 before use.  I've tested it on Mac OS
>> 10.6 with Python 3.2.3 and it seems to work.
>>
>> If you're running on Mac OS 10.8, well … now you can experience the same
>> non-existent window bugs in both Python 2.7 and Python 3.
>>
>>
> Sweet!  :-/
>
> I'll go see if the non-existent window bugs act the same on Python 3.
>
> ~ Nathan
>

-- 
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.

Reply via email to