On Samstag 21 November 2009, Wolfgang Rosner wrote: > > Pytools should be installed automatically along with 'python setup.py > > install'. If it didn't: do you have any idea why? > > not sure. > > could it be that I ran "make install" > instead of "python setup.py install" ?
"make install" invokes "python setup.py install". That shouldn't have been it. > (sorry, I'm just getting used to Python, preferred perl in earlier live) > > first I thought it was due to the different python path structures. > > standard on SuSE is > /usr/lib64/python2.5/site-packages/ > > but the egg-laying machine seems to put stuff to > /usr/local/lib64/python2.5/site-packages > instead > (maybe I could have reconfigured this, anyway) Weird. Curious about the reasoning behind this. > However, gl_interop.py did not run until I did > export PYTHONPATH=/usr/local/lib64/python2.5/site-packages/ > (was PYTHONPATH="" before) > > maybe this is since there is still the old python-opengl-2.0.1.09-224.1 > /usr/lib64/python2.5/site-packages/OpenGL/GL/ARB/ > ...with-no-vertex-buffer-in-there in the way which is caught before. > > But to figure it out I'm definitely lacking sufficient python experience. There is an easy trick to find out what file path actually gets imported: >>> import pytools >>> pytools.__file__ '/home/andreas/research/software/pytools/pytools/__init__.py' > hm, might give it a try. > I think best I could offer was be to prepare an own SuSE page with my > experience. Sure--just add a subpage under http://wiki.tiker.net/PyCuda/Installation/Linux (like the one for Ubuntu) > It all comes down to different ways and places where stuff is stored. > But I think my approach is not the best one, in the view back it were > better to configure new stuff so that it meets SuSE structure. Maybe. > Well, but this might break other dependencies? > Smells like big 'Baustelle'... > > So if your expectation of quality on your wiki is not too high, I'll post > my experience there. That's the whole point of a Wiki: information of questionable quality that people improve as they use it. It's a knowledge retention tool. Andreas
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ PyCUDA mailing list [email protected] http://tiker.net/mailman/listinfo/pycuda_tiker.net
