You are not logged in.
I maintain the PsychoPy package (https://aur.archlinux.org/packages/psychopy/). PsychoPy is an applicaiton written for python2 and an upcoming release will depend on the 1.2 alpha version of pyglet. The community repository already has python2-pyglet (https://www.archlinux.org/packages/comm … n2-pyglet/), but it is version 1.1.4 of pyglet. The AUR has pyglet-hg (https://aur.archlinux.org/packages/pyglet-hg/) and python-pyglet-hg (https://aur.archlinux.org/packages/python-pyglet-hg/) which both pull in the correct version of pyglet, but for Python3.
I would be willing to maintain a python2-pyglet1.2alpha (or possibly python2-pyglet-hg) package, but not sure if adding another pyglet package to the mess is really beneficial. Further, the same source of pyglet is used for both python2 and python3, so it seems like maybe the current AUR package should be a split package. Finally, all the packages "provde" pyglet and hence conflict with each other, but it is not clear to me why a python2 package should conflict with a python3 package. Is there a reason for this?
Offline