Richard Jones wrote: >On Friday 09 March 2007 10:43, Alex Holkner wrote: > > >>I'm going to have a go over this long weekend (Labour day in this part >>of the world) at panel-beating pyglet into something releasable as a >>"pyglet-pyweek" snapshot. This would be the reference library to use >>for PyWeek (if allowed by Richard at all) and would ensure continuing >>development on the trunk doesn't affect PyWeek participants. >> >>This snapshot would most likely not include any sprite, layout or gui >>code; so would require some knowledge of OpenGL to use. >> >>Any thoughts? Richard, any arbitrary deadline we should work towards >>for this snapshot? >> >> > >I've been thinking about this a lot over the last week and I'm leaning towards >not allowing use of a library that's released within a month of the comp >start. The reasons are several-fold, and particularly apply in this case: > >1. library devs have a real advantage, regardless of the level of > documentation, >2. bugs will pop up during the week and that will hurt both the library > user and dev, and >3. even if we snapshot to avoid API nukage, if there's bugs in the snapshot > that pop up down the track *someone* has to try to fix them and I know > I wouldn't be particularly interested in maintaining a fork at this > early stage. > >Does this seem reasonable? I want people to say no, 'cos I really want to use >pyglet in this pyweek too :) > > Perfectly reasonable, on second thoughts I'm with you on every point. I'll be entering PyWeek using some version of pyglet (possibly not even a snapshot), but disqualifying myself from the rankings etc.
Alex. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
