Here is the PR implementing the proposal: https://github.com/sagemath/sage/pull/38273
On Friday, June 21, 2024 at 12:49:37 PM UTC+9 Kwankyu Lee wrote: > Hi, > > From the discussion in > > https://github.com/sagemath/sage/issues/38211 > > motivated by the issue raised in > > https://github.com/sagemath/sage/pull/38207, > > we created a proposal to augment the current deprecation policy > > > https://doc.sagemath.org/html/en/developer/coding_in_python.html#deprecation > . > > Here is the proposal: > > (S) Only public functions, methods, attributes, classes living under sage are > subject to the deprecation policy. > > (M) Functions, methods, attributes, classes whose names start with an > underscore are considered internal, and is not subject to the deprecation > policy. > > (C) A class whose name does not start with an underscore is public by > default, but can be considered internal if experts agree that the class is > unlikely to be directly imported by user code. If experts disagree, then it > is public. For a PR changing the class, authors and reviewers are the > experts. > > > Moreover > https://github.com/sagemath/sage/issues/38211#issuecomment-2180309924 > defines the standard procedure for deprecation of public classes. > > > If no one has major objections, we will proceed to update the developer > guide to reflect the proposal. Comments are welcome. Thanks. > > > Kwankyu > -- 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/8e8a9a73-65d9-492d-a819-b0a716bab6e8n%40googlegroups.com.
