plugins.startup_modules checks that no new modules are being imported at startup.
As with most plugins, this requires some human judgement. We don't want to make the startup time any worse than what it already is. On the other hand, if your module is required by something that is already imported at startup it might not be feasible to avoid it. The plugin failure is a hint that you should try to use the lazy_import mechanism to avoid importing the module at startup. On Saturday, June 21, 2014 8:47:57 AM UTC+1, Ralf Stephan wrote: > > > > On Friday, June 20, 2014 8:10:18 AM UTC+2, Robert Bradshaw wrote: >> >> I just released a new version of the patchbot: >> http://sage.math.washington.edu/home/robertwb/patches/patchbot-2.2.spkg >> https://github.com/robertwb/sage-patchbot/compare/2.1.1.1...2.2 >> > > Nice. Can you please explain what happens with this PluginFailed? I cannot > see why... > http://patchbot.sagemath.org/ticket/2516/ > -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
