Re: Getting Octave to use Anaconda Python Environment

[Mike Miller]

On Tue, Apr 19, 2016 at 07:28:47 -0400, Ben Abbott wrote:
> > On Apr 18, 2016, at 11:18 PM, Colin Macdonald <address@hidden> wrote:
> > 
> > On 18/04/16 17:00, Ben Abbott wrote:
> >> I like the autoconf support. They allowed me to determine what
> >> depedencies were missing. The only problem for me was how to define
> >> $PYTHON. Can you modify configure to grab $PYTHON from the shell
> >> environment?
> >> 
> >> setenv PYTON python2.7
> >> system ./configure
> > 
> > This sounds like a good idea.  At run-time, we would need to support
> > that variable too, which could be useful.
> > 
> > *But* is $PYTHON env variable a standard thing?!
> > 
> > I didn't see it here:
> > https://docs.python.org/2/using/windows.html
> > 
> > Do you have a reference?
> 
> Do standards apply? I expect all you need is for “./configure —help” to 
> document what environment variables are supported.

No they don't. I think it would be useful to support a PYTHON
environment variable, which could either be the name of the executable
to search for on PATH (e.g. python3) or the full path to the Python
executable to use.

This could be useful for either configure, if kept, or at runtime, with
an error message instructing the user to "setenv PYTHON ..." and rerun
the command.

-- 
mike