Oh wow - I didn't realize that. I saw Python2.5-relevant code in the autofoo, but assumed no one was bothering to fix it because of the incoming cmake magic.
Anyway, making the line: #!/usr/bin/env python2 Seems to work on my system just fine - defaulting to the highest [2<=version<3] available. Cheers, Ben On Thu, Sep 22, 2011 at 1:34 PM, Tom Rondeau <trondeau1...@gmail.com> wrote: > On Thu, Sep 22, 2011 at 4:16 PM, Ben Hilburn <ben.hilb...@ettus.com>wrote: > >> This is a very simple / trivial fix. >> >> For distros with a native Python version of at least 3.0, the current >> gnuradio-companion executable will default to failing because it can't find >> the gnuradio site-packages in the Python 3.0 site-packages. >> >> This patch is a 3-character fix that makes 'env' explicitly return the >> executable to Python2.7. >> >> Note that if we are still supporting users that use Python2.6, this will >> fail, and this patch should be ignored. If this is the case, I'll add a note >> to the Wiki about fixing the Python path for Python3 users. >> >> Cheers, >> Ben >> > > Hey Ben, > Technically, we are still supporting Python 2.5, so this would affect > anyone running 2.5 or 2.6. > > Can you figure out a way of defaulting to _any_ version 2.x python, > instead? > > Thanks, > Tom > >
_______________________________________________ Patch-gnuradio mailing list Patch-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/patch-gnuradio
