I think we should fix that quickly, else we will have a significant flux of weird bugs/questions from people who don't realize they are not running what they think they are running. It will be extremely difficult for us (repliers) to understand the problems since, as shown above, the "Welcome to Yade VXXX" is showing an irrelevant VXXX.
Not clear to me: can we revert the current model where some yade modules are installed in standard python paths /usr/lib/python2.7/? This is the easiest fix, but I'm not sure what are the constraints from the packaging point of view. -- You received this bug notification because you are a member of Yade developers, which is subscribed to Yade. https://bugs.launchpad.net/bugs/1254708 Title: start-script picks wrong yade libraries in ubuntu 14.04 Status in Yet Another Dynamic Engine: New Bug description: If yade is compiled on 14.04 where yade stable is also installed, yade-mine executable will import the stable libraries present in /usr/lib/python2.7. It makes it impossible to use compiled version (maybe also problems to expect if different binary packages are installed). bchareyre@ubuntu:~$ yade/bin/yade-trunk Welcome to Yade 2013-11-21.git-6927b03 TCP python prompt on localhost:9000, auth cookie `cessad' XMLRPC info provider on http://localhost:21000 [[ ^L clears screen, ^U kills line. F12 controller, F11 3d view (use h-key for showing help), F10 both, F9 generator, F8 plot. ]] Yade [1]: yade.config.revision -> [1]: '0.97.0' Yade [2]: sys.modules['yade'] -> [2]: <module 'yade' from '/usr/lib/python2.7/dist-packages/yade/__init__.pyc'> To manage notifications about this bug go to: https://bugs.launchpad.net/yade/+bug/1254708/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~yade-dev Post to : yade-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp