Just to point out the obvious: If qringNF isn't enabled explicitly then it must be set by some singular package that is being imported in a test.
On Saturday, January 13, 2018 at 1:29:00 PM UTC+1, Simon King wrote: > > On 2018-01-13, Simon King <[email protected] <javascript:>> wrote: > > I wonder: Is the doctest framework adding certain options to > > Singular that are not used in an interactive session? If yes, > > how can I prevent that (at least during one test)? > > Indeed, I see this during the failing test: > singular.option() > //options: redSB redTail redThrough redefine loadLib usage prompt > qringNF > > whereas in a normal session the option qringNF is missing. What > really puzzles me: When I copy only the failing test into a file > then it passes. So, it seems that there are side-effect of the other > tests. But none of them is explicitly setting qringNF, and the > underlying code isn't using that option either. > > The Singular manual does not indicate whether qringNF is used by default > or not. > > So, do you have any idea why qringNF is sometimes unexpectedly used in > doctests and sometimes not? > > 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
