Hi, On 2014-05-13, [email protected] <[email protected]> wrote: > thanks for the info about checking the memory management, its quite useful! > It relates to the initial question about active testing, right? > Maybe it will help me to pinpoint some memory leak bugs in Singular.
This has already happened. It resulted in a patch that we applied to our singular spkg, and is now used upstream too, if I recall correctly. And when Sage's test suite finally passed with the debug version of Sage, I officially declared Singular "bug free" (tongue in cheek, of course). > In Singular a similar concept is implemented for the new ASSUME keyword. > So if I call in Singular "ASSUME(3, 1==2);" '1==2' is only checked if the > (package-local) *assumeLevel* is >=3. > > Since I'm new to sage, > I'm questioning if sage has a similar framework ( if you are picky, the > question belongs to sage-support or to ask.sage ) > and if sage does not have such a framework, I suggest to think about it and > then its probably in the right place at sage-devel What often is done is to provide an optional argument "check" for a constructor, and to skip tests if "check=False". However, this is (and should be!) a case-by-case decision, since it is mainly used if a constructor is called from a function that has already asserted that the input for the constructor is valid, so that skipping the assertion in the constructor is ok. I don't think Sage has a global "assertlevel", though. Best regards, Simon -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
