Also, I have created a pyglet-devs groups as a speculation in whether
people were interested in the separation. Not sure if people are yet
but I thought I'd advertise it again.

Richard.

On Aug 15, 12:31 pm, Richard Thomas <[email protected]> wrote:
> I agree with Tristam. Getting a working 1.2 release would be good.
>
> Cleaning up the issue tracker would be a good first step though, even
> going through and giving some of them a status would be useful.
>
> Richard.
>
> On Aug 15, 12:22 pm, Tristam MacDonald <[email protected]> wrote:
>
> > On Sat, Aug 15, 2009 at 7:02 AM, Alex Holkner <[email protected]>wrote:
>
> > > I would rate the stability of trunk at somewhere approaching an alpha
> > > release for device and platform testing.  For what it's worth, my
> > > latest PyWeek entry used pyglet 1.2dev internally and no issues were
> > > reported (the game had a fairly involved audio component, too).
>
> > It sounds to me as if we should focus our efforts on bringing trunk up to a
> > full release, and put 1.2dev on hold for the immediate future.
>
> > However, the 1.2 canvas and libs refactor sounds very promising, so I
> > wouldn't want to trash it entirely.
>
> >  - The process for creating distributable Windows and OS X packages is
>
> > > extremely time-consuming and error-prone (it is documented in
> > > doc/internal).  I would suggest dropping these distributions for just
> > > the tar.gz/zip packages for developers to drop into their projects.
> > > However the download counts for the installation packages are much
> > > higher than the source/egg packages.
> > >  - Speaking of egg packages, these should also be dropped in future;
> > > download counts are low and setuptools/easy_install is extremely
> > > fragile, leading to broken installations that are difficult to repair
> > > if you don't know where to look.
>
> > I am willing to maintain the Mac binary packages at least - installation
> > needs to be kept simple for beginners, so would be good if someone can adopt
> > the Windows binary as well.
>
> > I would also like to keep easy_install around - it shouldn't be flaky, and
> > perhaps there are some changes we can make to help with that.
>
> >  - A Py3K conversion would be quite a lot of work.
>
> > I don't think that is a huge loss - Py3k has remarkably little traction thus
> > far in the game development field.
>
> > --
> > Tristam MacDonaldhttp://swiftcoder.wordpress.com/
--~--~---------~--~----~------------~-------~--~----~
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