On Wednesday, April 23, 2025 at 2:35:48 PM UTC-5 Dima wrote: I haven't built any Python dependencies (unless testing stuff) for years, and I suppose this applies to the vast majority of people doing Sage development or installation from source. Why do you need to build them? Can you start with an environment which has them? Homebrew, Conda... Else, you can build them by hand in /usr/local/.
I have no idea what you are talking about. I have already built a relocatable python which is suitable for embedding into a macOS App bundle. I am trying to get sage to use that python as its "system python". I don't need to build any python dependencies. The topic of "dependencies" arose only because the dependency checker in Sage's python3 spkg erroneously concluded that it must install the python3 spkg, instead of using the python I built and asked it to use, because it could not find what it thinks are the dependencies of my python. In other words, the dependency checker in the python3 spkg is broken for my application. So I followed Michael's suggestion (more or less) by disabling that dependency check. I was then able to get halfway through a sage build based on my python. The build failed when it got to the first pip spkg, I have now discovered that the problem was that the sage pip spkg installed pip into the wrong venv. It reinstalled pip in a personal venv of mine, instead of installing it in the sage venv, presumably due to some environment variable screw up. So I don't need any new advice on how to deal with python dependencies and I have no idea why you are bringing them up now, long after it was all explained by Michael. - 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 visit https://groups.google.com/d/msgid/sage-devel/4278fcd2-a7f2-47db-bdef-8f638668adbbn%40googlegroups.com.
