1) Having sagemath detect python version requirements and build its own if not acceptable version is found leads to increased support requests.
[...] It seems to me that for 1) it isn't so important if python occurs as an spkg or not -- the main issue there would be resolved if the build process would not default to initiating building python. So it would seem that it's simply the python version detection code that can be adjusted. We could just have a configure flag "--install_own_python" to allow the prerequisite requirement to be fulfilled by building the python spkg; an option that would by default be off. Building on this idea, I wonder if there should be a mechanism along the lines of: When compiling on macOS and homebrew is present, check if *all* the recommended homebrew packages <https://doc.sagemath.org/html/en/installation/source.html#macos-package-installation> are present and only proceed if they are or the person provides the flag "--proceed-at-own-risk". In the particular case that Dima highlighted, Python was actually the second spkg not to build; the first was gsl which is one of the recommended homebrew packages. Best, Nathan P.S. I'm assuming that the issue compiling Python are specific to macOS and that OS's failure to provide openssl as a system library. Dima please correct me if that you are also seeing Python compilation errors on Linux. -- 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/afd71c29-8424-4dfd-901e-f058df5107b8n%40googlegroups.com.
