On Saturday, February 10, 2024 at 2:56:57 PM UTC-8 Dima Pasechnik wrote: yes, make them standard, but keep them pip packages (i.e. no version pinning, no tarballs/checksums).
By current policy, "standard" packages cannot be "pip" packages. This is documented in https://deploy-livedoc--sagemath.netlify.app/html/en/developer/packaging#package-source-types I believe the reason is that it would conflict with the longstanding practice of the project to ship Sage releases in the form of a self-contained source tarball, from which Sage can be installed in an environment without network access. I will note that I personally never use these tarballs (nor have I recommended to anyone to use them), but historically it has been the expectation of the community. See for example the 2016 sage-devel thread https://groups.google.com/g/sage-devel/c/C7-ho1zvEYU/m/Ep8i-cbHAgAJ on a similar topic. So for the purpose of the present poll, let us assume that the packages would be added as standard "wheel" packages. -- 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/9c168211-265f-4748-88d0-b0dadc91bfb0n%40googlegroups.com.
