I had to fix this for another bug, I have not tested with use_broot=false but in theory we should be always using the virtualenv python now.
On 10 March 2014 01:27, Daniel Narvaez <[email protected]> wrote: > Oh interesting! osbuild is actually using a virtualenv. I suspect it > doesn't work because we are not activating it but just running the python > executable in the virtualenv. So osbuild is using the virtualenv python, > but the child processes are not. Now if I could remember why we are not > activating the virtualenv... :) > > Still I think the cleanest solution is to make sugar-base require python2 > explicitly. It will also work if you are building archlinux (or gentoo) > packages. > > > On 10 March 2014 01:14, S. Daniel Francis <[email protected]> wrote: > >> All Arch Linux users I met usually solve this problem when developing >> by using virtualenv. >> >> 2014-03-09 20:54 GMT-03:00 Daniel Narvaez <[email protected]>: >> > On 10 March 2014 00:46, Daniel Narvaez <[email protected]> wrote: >> >> >> >> On 10 March 2014 00:07, Gonzalo Odiard <[email protected]> wrote: >> >>>> >> >>>> >> >>>> Then issues ocurred with gwebsockets. It persistently tried to use >> >>>> python3.3, my system's default, instead of python2.7. Finally I >> found the >> >>>> culprit, in >> >>>> ./out/sandbox/install/lib/python2.7/site-packages/osbuild/build.py I >> >>>> replaced in line 190 one instance of "python" for "python2.7" and it >> worked >> >>>> after that. >> >>>> >> >>>> Finally when building sugar-base I had to set up the environment >> >>>> variable PYTHON=/usr/bin/python2.7 in order for it to build. >> >>>> Also, when building sugar, I had to manually create the directory >> >>>> "./out/install/etc/gconf/" or it would fail to install >> >>>> >> >>> >> >>> Maybe you can solve this issues just creating symlinks like in fedora: >> >>> >> >>> [gonzalo@localhost develop-activity]$ ls -l /bin/python >> >>> lrwxrwxrwx. 1 root root 7 Jan 9 2013 /bin/python -> python2 >> >>> >> >>> [gonzalo@localhost develop-activity]$ ls -l /bin/python2 >> >>> lrwxrwxrwx. 1 root root 9 Jan 9 2013 /bin/python2 -> python2.7 >> >>> >> >>> Gonzalo >> >> >> >> >> >> I think archlinux has those symlinks already, but it also has "python" >> >> which is reallly python 3. >> >> Now honestly I think that's a very bad decision archlinux made (and the >> >> reason I'm not using it anymore, fwiw, it's a real pain if you are >> compiling >> >> stuff a lot). >> >> But it is compatible with best practices suggested by the python >> >> documentation. So I think we should follow those practices in >> sugar-base >> >> (i.e. explicitly require python2), which will take care of this issue. >> We >> >> are already doing that in the gtk3 modules. >> > >> > >> > Oh missed the /bin/python -> python2 suggestion. That would break >> archlinux >> > stuff which assumes python is python3. >> > >> > _______________________________________________ >> > Sugar-devel mailing list >> > [email protected] >> > http://lists.sugarlabs.org/listinfo/sugar-devel >> > >> > > > > -- > Daniel Narvaez > -- Daniel Narvaez
_______________________________________________ Sugar-devel mailing list [email protected] http://lists.sugarlabs.org/listinfo/sugar-devel
