On 2017-03-01 11:47, Simon King wrote:
I don't think they are that much different in spirit. In all cases, the single underscore methods are for implementing functionality in a Sage-specific way
No, you are misunderstanding. There is absolutely nothing Sage-specific about _pari_. In fact, I started this discussion because we would like to split up the PARI interface as a different package, independent from Sage. And the Sage convention _pari_ would not make much sense then.
On the other hand, _repr_ or _mul_ are only defined for subclasses of SageObject, so therefore they are Sage-specific.
a "visible" one (.pari()) in the case of _pari_
There is no such thing as a .pari() method. Maybe you are confusing with the pari() global function? But then I would argue that the situation is very similar to str or int: Python has global functions str() and int() calling .__str__() and .__int__() methods. Which is *exactly* analogous as what pari() does: it currently calls a ._pari_() method. Given the analogy I just explained, this should be changed to .__pari__().
-- 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.
