FYI I found a way to more robustly handle the situation by grabbing the path to the interpreter by using sys.executable. This seems to work nicely and I like this solution better.
http://gnuradio.org/cgit/jblum.git/commit/?h=wip/grc/python_interp_path -Josh On 04/15/2011 12:06 PM, Ryan van den Bergh wrote: > Hi Josh, > > I've already got python in my path. I agree it's a mystery - I'll just chalk > it up to another reason why I really hate Windows! > > I'll just run it manually. I'll make a batch file to do it so that it's not > too painful. > > Thanks for the assistance though, I really appreciate it! > > Kind regards, > > Ryan > > On Fri, Apr 15, 2011 at 8:57 PM, Josh Blum <[email protected]> wrote: > >> >> >> On 04/15/2011 11:10 AM, Ryan van den Bergh wrote: >>> Hi Josh, >>> >>> Thanks for the suggestions! >>> >>> I can run top_block.py from the command line, and I've saved it in My >>> Documents folder, however I still can't get GNU Radio Companion to >> execute >>> the file. Do I perhaps have to do something special when running the >>> gnuradio-companion.py file? >>> >> >> Glad to hear it works. So, GRC is calling into python to exec the >> generated python code. Its trying to run "python <path to your file>... >> And this works on linux because python is in your path, but I have no >> idea why this works on windows. I mean obviously not for you, but its a >> mystery as to why it works for me. Python is not in my path. I have no >> idea how grc manages to execute the file it generates. But somehow it >> does... >> >>> The command I'm using at the moment is: D:\Python27\python.exe >> "C:\Program >>> Files (x86)\gnuradio\bin\gnuradio-companion.py" >> >> I would stick to running it manually like this until I figure this >> mystery out. You may try putting c:\python27 in your %PATH% >> >> -Josh >> > _______________________________________________ Discuss-gnuradio mailing list [email protected] http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
