On Mon, Aug 15, 2016 at 10:09 AM, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > On 2016-08-15 20:25, William Stein wrote: >> >> It would be more standard to have an >> explicit library import, which -- on import -- would print out >> something about it being experimental and unstable. > > > Whether it's a separate library or part of Sage doesn't really matter for > this discussion. So I read this as being in favour of marking the complete > module as experimental. >
Good point. Also, I'm for making the user type import something.or.other **explicitly**, rather than having it pre-imported on startup. Of course, the import command will be documented. -- William > > -- > 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 sage-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- William (http://wstein.org) -- 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 sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
