On Thu, Mar 5, 2020 at 8:56 PM Alexander Kruppa <akru...@gmail.com> wrote:
>
> I think we're getting closer.
>
> alex@lily:~/build/sage-develop> ./sage -sh
>
> Starting subshell with Sage environment variables set.  Don't forget
> to exit when you are done.  Beware:
>  * Do not do anything with other copies of Sage on your system.
>  * Do not use this for installing Sage packages using "sage -i" or for
>    running "make" at Sage's root directory.  These should be done
>    outside the Sage shell.
>
> Bypassing shell configuration files...
>
> Note: SAGE_ROOT=/home/alex/build/sage-develop
> (sage-sh) alex@lily:sage-develop$ echo $PATH
> /home/alex/build/sage-develop/build/bin:/home/alex/build/sage-develop/src/bin:/home/alex/build/sage-develop/local/bin:/home/alex/.pyenv/shims:/home/alex/.pyenv/bin:/home/alex/.local/bin/:/home/alex/.pyenv/shims:/home/alex/.pyenv/bin:/home/alex/.local/bin/:/usr/lib64/mpi/gcc/openmpi/bin:/home/alex/bin:/usr/local/bin:/usr/bin:/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin
> (sage-sh) alex@lily:sage-develop$ which gp
> /home/alex/build/sage-develop/local/bin/gp
> (sage-sh) alex@lily:sage-develop$ which python
> /home/alex/.pyenv/shims/python
> (sage-sh) alex@lily:sage-develop$ python
> Python 2.7.14 (default, Oct 12 2017, 15:50:02) [GCC] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> from distutils.spawn import find_executable
> >>> find_executable('gp')
> '/usr/bin/gp'
> >>>
>
>
> "python" runs the distribution's Python 2. There is no Python 2 installed in 
> SAGE_LOCAL/bin/
>
> alex@lily:~/build/sage-develop> ls -la 
> /home/alex/build/sage-develop/local/bin/py*
> lrwxrwxrwx 1 alex users     8 Mar  3 22:08 
> /home/alex/build/sage-develop/local/bin/pydoc3 -> pydoc3.7
> -rwxr-xr-x 1 alex users   109 Mar  3 22:08 
> /home/alex/build/sage-develop/local/bin/pydoc3.7
> lrwxrwxrwx 1 alex users     9 Mar  3 22:08 
> /home/alex/build/sage-develop/local/bin/python3 -> python3.7
> lrwxrwxrwx 1 alex users    16 Mar  3 22:08 
> /home/alex/build/sage-develop/local/bin/python3-config -> python3.7-config
> -rwxr-xr-x 1 alex users 31304 Mar  3 22:07 
> /home/alex/build/sage-develop/local/bin/python3.7
> lrwxrwxrwx 1 alex users    17 Mar  3 22:08 
> /home/alex/build/sage-develop/local/bin/python3.7-config -> python3.7m-config
> -rwxr-xr-x 1 alex users 31304 Mar  3 22:07 
> /home/alex/build/sage-develop/local/bin/python3.7m
> -rwxr-xr-x 1 alex users  3143 Mar  3 22:08 
> /home/alex/build/sage-develop/local/bin/python3.7m-config
> lrwxrwxrwx 1 alex users    10 Mar  3 22:08 
> /home/alex/build/sage-develop/local/bin/pyvenv -> pyvenv-3.7
> -rwxr-xr-x 1 alex users   466 Mar  3 22:08 
> /home/alex/build/sage-develop/local/bin/pyvenv-3.7
>
>
> My pyenv points at the system-installed Python 2:
>
> alex@lily:~/build/sage-develop> pyenv global
> system
> alex@lily:~/build/sage-develop> pyenv shell
> pyenv: no shell-specific version configured
> alex@lily:~/build/sage-develop> pyenv local
> pyenv: no local version configured for this directory
>
>
> The config.log file (attached) for the build of the development version says:
>
> [...]
> configure:8367: checking Python version to install
> configure:8384: result: 3
> [...]
> configure:29199: result: python2-2.7.15.p1:                           does 
> not support check for system package; optional, use "./configure 
> --enable-python2" to install
> configure:29199: result: python3-3.7.3.p1:                            does 
> not support check for system package; will be installed as an SPKG
> [...]
>
> It looks like Python 2 does not get compiled as part of Sage, and merely 
> running "python" (as opposed to, say, "python3") from the Sage shell ends up 
> using the system-installed Python 2 which then runs the system-installed gp.
>
there is no need for Python2 any more. Perhaps your
/home/alex/.pyenv/shims/python
is very unusual, and it modifies/freezes PATH, or something like this...

What's the output of
>>> import os
>>> os.environ['PATH']

if you run it?

Anyhow,  /home/alex/.pyenv/shims/python looks dodgy to me.
I don't think we ever test anything for pyenv...






> --
> You received this message because you are subscribed to the Google Groups 
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/ec5c50d6-46b8-4534-a9fe-81aa12c255ab%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq24__7OjTxKteyDB%2Bw5y0DUopd%3D7S1UwhWU%3DZ1kVdEnGQ%40mail.gmail.com.

Reply via email to