Re: [Patch-gnuradio] Fixing GRC Executable for OSes with Native Python >= 3.0

[Ben Hilburn]

Blerg. Short of writing a python script to invoke a python script, then, either one party or the other is going to have to modify env variables, make a symlink, or change the top line of code.

Perhaps for now we should just assume that the Python >= 3.0 users are l337 enough to handle it, and let it default to working out-of-the-box to you Python <= 3.0 slackers? ;)

If you'd like, I'll make a note in the Wiki about it and we can leave this one be for now?

Cheers,

Ben

On Thu, Sep 22, 2011 at 1:42 PM, Tom Rondeau <address@hidden> wrote:

On Thu, Sep 22, 2011 at 4:36 PM, Ben Hilburn <address@hidden> wrote:

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

Hmm... not working on my Ubuntu 10.04 (running Python 2.6).

Tom

 

On Thu, Sep 22, 2011 at 1:34 PM, Tom Rondeau <address@hidden> wrote:

On Thu, Sep 22, 2011 at 4:16 PM, Ben Hilburn <address@hidden> 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