Just for some history / initial motivation: pyglet was always intended to be a *pure python*, no compilation, no binaries install. If it wasn't then obviously it'd have been developed using cython instead of ctypes, duh ;-)
On 13 November 2015 at 12:22, Benjamin Moran <[email protected]> wrote: > I would guess that the built-in png and wav support is probably adequate > for most users. > > This topic does bear discussion though, because avbin isn't even > available is some Linux distribution repositories. On Arch, for example, it > must be built from the AUR. This wouldn't matter if it was redistributable > without worry, but it seems that it's ambiguous. > > I like the idea of separate dependencies for each codec as you've listed. > I guess it all comes down to maintaining it. > > -- > 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 http://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 http://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
