On Thursday, July 14, 2022 at 5:30:47 AM UTC-7 marc....@gmail.com wrote: > When I did an incremental build with the venv-python3.10.3 in place, a new > venv named python3.10.5 was created. But that new venv depends on the old > 3.10.3 venv. In fact, there are at least 16 executable files in > sage/venv-python3.10.5/bin for which the shebang points to > sage/venv-python3.10.3/bin/python3 > This prevents sage from working after the 3.10.3 venv is removed. >
> I am guessing that these bad shebangs are created because the old venv is > actually being used to build the new venv. > No, I don't think that's what's happening. It's probably just that the scripts are cached in pkgs/sagemath-standard/build/scripts/ Try "make sagelib-clean". -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/8960ed12-d6b1-4f3a-a98e-62224c411375n%40googlegroups.com.
