On Jan 8, 2008 4:10 PM, Andrew Straw <[EMAIL PROTECTED]> wrote: > Just so that I understand the policy on new features in pyglet: Is the > idea that a feature's foreseen user base must be broad before inclusion? > Or is this a pre-1.1 austerity measure? Or a fear of lack of maintainers > for new code? Or something else?
Some combination of the above, as well as keeping pyglet within scope (it's not a random collection of functions that people find useful), and modulo my personal bias, mood and the time of day ;-) Martin Spacek wrote: > Also, it's a feature in pygame/SDL, so > people coming over from that library will expect to see it in pyglet. I > was actually surprised by its absence. IMO it being a feature in PyGame is as much reason to leave it out as to put it in (i.e., I'm not trying to duplicate that library; it already exists and is mature). 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 -~----------~----~----~----~------~----~------~--~---
