On Thursday, June 8, 2023 at 4:40:06 PM UTC-7 Michael Orlitzky wrote: Pip [...] can't do anything with the non-python software on which sage subsists. To make sage-via-pip work, we'll have to maintain a new pseudo- distribution on pypi that either ships people pre-built wheels or wraps autotools/cmake/etc in python. As was made clear in recent threads, many developers don't want to be maintaining the *first* sage distribution, much less a second one.
That's right, building binary wheels to be distributed on PyPI (in addition to the source distributions) will be one of the key steps in order to make it very user-friendly -- i.e., on par with doing "pip install scipy" on standard platforms. It is normal practice of Python projects to create binary wheels and make them available on PyPI. There is sufficient mainstream infrastructure (such as https://github.com/pypa/cibuildwheel) that makes it easy. And it is, in fact, even easier for us (almost free) because we can reuse the Sage distribution for this; we do NOT have to write new ad-hoc installation scripts for the non-Python dependencies. For example, I have recently provided a wheel-building workflow for an upstream project, PySCIPOpt, that does exactly this. https://github.com/scipopt/PySCIPOpt/pull/652/files#diff-50c86b7ed8ac2cf95bd48334961bf0530cdc77b5a56f852c5c61b89d735fd711R16 -- 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/efdc3b85-5690-49f7-814b-f5602dd89ee0n%40googlegroups.com.
