Thanks for the response! Sorry for my delayed reply. We're using Python 3 on Windows 7, our python distribution is Anaconda. My previous test used the pyglet installed by "pip install pyglet", which I believe installed 1.2.4
To test your suggestion, we created a virtual environment, and tried installing from the source instead of the latest stable 1.2.4. To do this, we used the following two commands: conda create -n pyglettest python=3.4 pip install +hg:https://bitbucket.org/pyglet/pyglet Trying to import pyglet failed, unless my working directory was the directory where I had cloned the repository. It seems that pip install is not putting all of the repo into site packages in the way that I'd expect; in particular, the extlibs directory didn't contain future after pip install, but it was present in the repository. If I copied the future directory from extlibs into the place in site-packages where things were installed, then pyglet now imports. Incidentally, setup.py for the repo shows a version of 1.3.0a, but pyglet/__init__.py sets pyglet.version = 1.2.2. The high CPU usage following "import pyglet.image" still appeared to be present. On Sun, Nov 22, 2015 at 10:52 PM, Benjamin Moran <[email protected]> wrote: > Hi Andrew, > > You're on Windows 7, right? I just gave this a try on my Windows VM and > could not replicate it. According to Windows Resource Monitor, the Python > process CPU usage only blips up for a split second, then drops back down to > 0%. > > I tested on Win 7 Ultimate 64-bit, using the current default pyglet > branch. If you're using the last stable pyglet release, could you give it a > try with the lasted code from Bitbucket? > > -Ben > > > On Monday, November 23, 2015 at 5:32:53 AM UTC+9, Andrew York wrote: >> >> Hello, I'm new to the community, but I'm a very happy pyglet user for >> some time now. I've asked a pyglet question on stack overflow: >> >> http://stackoverflow.com/questions/33833646/why-does-referring-to-a-class-in-python-pyglet-image-cause-heavy-cpu-load-on-w >> It seems sensible to mention it here also. >> >> I'm not familiar with pyglet's internals, but I'm happy to do what I can >> to help answer this question. >> >> Thanks for making this excellent project. >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "pyglet-users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/pyglet-users/20USjzHTy5g/unsubscribe. > To unsubscribe from this group and all its topics, 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.
