We added python_build as an optional "pip" package (see 
https://deploy-livedoc--sagemath.netlify.app/html/en/developer/packaging#package-types
 for 
the terminology),
- 
https://deploy-livedoc--sagemath.netlify.app/html/en/reference/spkg/python_build#spkg-python-build
 (added 
in 2022).

"python_build" (a.k.a. pypa/build) is the current standard front-end for 
making source distributions and wheels from a Python source tree. It has 
replaced the deprecated practices of calling "setup.py sdist" or "setup.py 
bdist_wheel" directly. We already use it for building the modularized 
distribution packages. Making it a standard package will allow us to 
modernize the build infrastructure (front-end) for the Sage library in the 
Sage distribution.

I'm proposing to make it a standard package according to the procedures in 
our developer guide. Per our policy, that's a "normal" package, so its 
dependency pyproject_hooks will also be added. The PR is prepared 
in https://github.com/sagemath/sage/pull/37300 

This is a re-do of my proposal 
https://groups.google.com/g/sage-devel/c/MIU-xo9b7pc/m/NsyUa7iXAgAJ whose 
discussion was stalled by commenters bundling it with political demands. 

-- 
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/e6b74134-7ed7-4da4-8b41-bebeef5c1f15n%40googlegroups.com.

Reply via email to