Oh. And I think the default value should probably be set with:
PYTHON_FOR_VENV=/usr/bin/false
- Marc
On Saturday, May 4, 2024 at 5:54:55 PM UTC-5 Marc Culler wrote:
> It is disturbing when one sees "command not found" errors in a configure
> script. That is what happens with 10.4.beta5. After tracing it down I
> found that they are coming from lines like:
>
> * if "${PYTHON_FOR_VENV}" -c "import sys;
> sys.exit(sys.version_info.minor < 11)"*
> *then :*
>
> The variable PYTHON_FOR_VENV is set with the command:
>
>
>
>
> *if test x$sage_spkg_install_python3 = xnothen :
> PYTHON_FOR_VENV="$ac_cv_path_PYTHON3"*
>
> But I think that if sage_spkg_install_python3 has the value yes then
> PYTHON_FOR_VENV is not assigned a value, causing the errors when configure
> is run.
>
> I have not determined what the collateral damage of this is. But it seems
> to me that there should be a default value for PYTHON_FOR_VENV.
>
> - Marc
>
--
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/54e45b0d-1cdf-407d-9cfb-a312397c64e3n%40googlegroups.com.
