Closed thomasdeneux closed 3 years ago
Have you tried updating your video drivers? It really seems like OpenGL just really isn't playing nicely with python and what vispy expects. I'm also confused by the paths in the traceback. Shouldn't there be a python36
directory after lib
or does Windows not do that?
Unfortunately we have already updated the video drivers. We will attempt to uninstall / clean reinstall them though. Regarding the paths, it is because we use a Python environment (conda-alphai
) to run our code that python36
does not appear in the path.
On OSX I have environments with ~/anaconda/envs/vispy_py37_pyqt5/lib/python3.7/site-packages/
so it seemed a little strange. I've never seen that before.
Has there been any progress on this issue? We're running into similar error messages with some of our windows users and our windows CI which uses vispy in this way. See https://github.com/napari/napari/pull/551
I don't have a windows machine readily available, but might be able to access one soonish to start trying to figure this out a little more. It's also not clear to me what specific windows configurations are affected by this issue, but I see in vispy it's been talked about in #1342, #1450, and #1503.
Hello, no there was no progress, we were not able to run vispy on the above-mentioned computer. I could not find helping information from the mentioned related issues (though at the present time i do not remember all the details).
In fact we have about ten similar reconditioned computers that are a few years old, and were we able to run vispy only on one of them. We would appreciate any progress in figuring out what happens, as we would still like to run vispy on the other computers.
@sofroniewn What type of python environment are you running on in your CIs and for your users?
As far as I remember when this original distutils error shows up it is because the GL version isn't getting reported to python/vispy/pyopengl/etc from the OpenGL drivers. It is possible that OpenGL isn't being initialized in some way that these drivers need (like showing the active GL canvas before asking what version it is), but it seems odd that other systems/drivers would behave fine. It also seems like intel integrated graphics are usually involved when things go wrong. Perhaps it is something specific (known issue :crossed_fingers: ) in the intel drivers.
(at a conference this week so might not have time to look in to this)
@djhoese we're looking to support python 3.6 and 3.7 for osx, linux, and windows as broadly as is reasonably possible, and at least understand the cases where it isn't possible so we can tell users before they needlessly struggle.
For our CI, we're using cirrus CI to run it, with the configuration of our windows options here - https://github.com/napari/napari/blob/785891502e0870e682f30c124a5c339576db4715/.cirrus.yml#L44
The person who setup our CI is out right now, but maybe @jni can help too.
Closing since it sounds like these GPUs are too old, but let's reopen if people think there is more to it or we could improve the error message(s)
Hello,
I installed vispy on a computer that is a bit old (Lenovo Thinkpad T410 2537) and run into trouble with OpenGL.
OpenGL Extensions Viewer sees the following:
SYSTEM
OPENGL
Trying the examples/basics/gloo/start.py gives
AttributeError: 'LooseVersion' object has no attribute 'version'
error.Checking
vispy.sys_info()
raises apyglet.gl.lib.GLException
error.I could not figure out from other related issues where to go from here, so may i request some help here.