On Wednesday, March 1, 2017 at 2:59:07 AM UTC-8, Jeroen Demeyer wrote: > > > 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. > > Well, it is in fact sage-specific at the moment. However, what you're proposing is that an independent package (pyri?) would be spun off. It looks to me that the renaming should (at least initially) be limited to that package. Essentially this package would introduce a new protocol (conversion from/to the pari library) and third party classes can participate in this protocol by implementing a "_pari_"/"__pari__" method. Using "__pari__" seems reasonable, but you might want to look for precedents of implementations that use that naming conventions for protocols that are only supported by add-on libraries (most such protocols I know of, like "iterator", are supported by python out of the box).
If you go with "__pari__" then objects in sage (at least for the time being) would have "_pari_" as an alias, for compatibility reasons, but that has little to do with pyri. In fact, using something other than "_pari_" could be advantageous: you can tweak the API of pyri until you hit 1.0 and we'll have the namespace room in sage to put the appropriate shim between "_pari_" and your chosen protocol method name. It does seem to me that your desire to choose a different name is mainly driven by the fact that the pari interface is spun off, which is not the case for other interfaces at the moment. So I think it makes most sense to limit the discussion to just the pari interface. -- 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.
