On Wed, Apr 27, 2016 at 5:05 PM, William Stein <[email protected]> wrote: > On Wed, Apr 27, 2016 at 7:09 AM, Kwankyu Lee <[email protected]> wrote: >> This discussion is hardening the terms: Sage core and external packages. But >> from the point of view of the people developing the would-be external >> packages, the official term would better be >> >> Sage extension, >> Sage library extension, >> Sage library extension package, >> or SLEP.
Two easily confused with "extension module" in the sense of a Python module written in C. >> Or simply extension package. > > Or > > Python package (that depends on Sage) Well remember there are two types of projects we're talking about here: 1) Projects that adhere to some yet-to-be-determined standards set out by the Sage project, and that in return are promoted as extra, if not more specialized products built on Sage, included in Sage-the-distribution, and possibly used in continuous integration with Sage as well. Those would deserve a special name "affiliated package" or the like. 2) Packages that happen to "import sage" somewhere. Those I agree are Python packages (that depend on sage). Best, Erik -- 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.
