On Tuesday, February 28, 2017 at 8:26:22 AM UTC-8, Jeroen Demeyer wrote: > > (4) __pari__(): consistent with Python (__int__, __str__) and NumPy > (__array__). However, creating such names possibly goes against the > Python documentation [2]. > > This would leave with me the strong expectation that the advised way of invoking this method is via pari(<thing>), which of course could work. It just means that, for instance, gap(a) would translate to a.__gap__(G=gap) [in cases where there are multiple interfaces around].
I'm not sure it's an improvement. Is _pari_ so likely to clash with other packages? It doesn't seem any of the alternatives come out as great winners either, and they have their own issues. So it seems to me changing the names will be a lot of work with very limited actual benefit. -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
