Emmanuel Charpentier wrote: > Should this be discussed again, with a call for *VOTE* ?
I don't think this is something that can be decided independently of other conventions (such as the semantics of equality and comparisons and the handling of inexactness). At the very least, I think someone would have to dig through the archive of sage-devel and summarize the arguments brought up in previous discussions before it would make sense to vote. But I agree that there is a strong need for clarifying and documenting this kind of general conventions. I find it really frustrating, both as a user and an occasional contributor, to see the developer guide discuss at length things like the use of git, trac and cython (that are not specific to sage) and say so little about sage conventions on things that need to be handled consistently over the whole codebase (to name but a few: "unknown" results and comparisons again, current vs deprecated best practices, coercions involving "special" parents like SR, InfinityRing or interfaces, branches of analytic functions, semantics of real and complex parents, of variable names [wrt comparison and coercion], of methods like is_field() or is_exact(), when to use conversion and when to use coercion in library code...). -- Marc -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
