Hi,

I am currently refactoring (and completely unit testing) the direct sound
driver. So some breakage might occur indeed. I am actually doing that on
Windows 10, so I will notice the breakage. Before 1.3 is released all the
issues should of course be resolved.

The codebase is indeed now py2-3 compatible. Mostly tested on Linux and
OSX, Windows is my current target.

Disruptiveness of changes between 1.2 and 1.3 should be minor, but we are
cleanin up some technical debt and modernizing some parts. I think I should
at least try using latest cocos to verify.

Before releasing 1.3 I will also make sure a good changelog is available.

Rob

On 22 March 2016 at 22:06, claudio canepa <[email protected]> wrote:

> With the current tip of pyglet master at bitbucket
>
> (
> K:\cocos_pristine\pyglet\examples>hg parents
> changeset: 3429:f10760f57976
> tag: tip
> user: Rob van der Most <[email protected]>
> date: Tue Mar 15 17:08:11 2016 +0100
> files: pyglet/media/drivers/directsound/__init__.py
> description:
> Use generic player worker for DirectSound driver
> )
>
>
> Running on win7-64bits I got tracebacks running example/image_display.py,
> both in py 2.7.11 64 bits and py 3.5.1 64 bits
>
> traceback in py27-64bits: http://pastebin.com/QQu28iDJ
> traceback in py35-64bits: http://pastebin.com/Z1ryM9UZ
> traceback in py27-32bits: http://pastebin.com/XU1vGntf
>
> Looking at commit logs seems that a heavy refactor is on course, so:
>     1. master is supposed to work right now on windows ?
>
>     2.  changes is setup.py seems to imply that the current codebase is
> directly compatible with py3 and py2 (no 'use_2to3' or other
> transformations necessary), is that correct ?
>
>     3. The pyglet version in setup.py is 1.3,0a1 . I noticed changes in
> pyglet's Sprite properties breaks cocos's Sprites, so, how much disruptive
> are meant to be the changes from 1.2 to 1.3 ?
>
>     4. any tip to manage transition from 1.2 to 1.3 ?
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "pyglet-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/pyglet-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"pyglet-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/pyglet-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to