Is there some sort of debug flag set when using jmol? If I click on a 3d > graphic in the notebook, I get half a dozen messages like this in the > console: > > This was first reported at http://trac.sagemath.org/ticket/16004#comment:74 . I didn't feel comfortable removing the debug statements since that was Volker's addition, and debug statements are fine, we have other places we put in messages of a similar nature. The problem is, as he points out, that somewhere else "DEBUG-level logging by default" was enabled - I don't think this is just in sagenb, though, and I don't know how to get rid of it.
But if you can find where that switch was turned on easily and then turn it off simply, perhaps our intrepid release manager will consider it? I find it annoying but am not worried about it, since Sage produces lots of other chatter/warnings when compiling that I find more worrisome, while this is expected and shows things are working. By the way, you should only see these in Chrome/Chromium; for some reason we never need to get to that particular code in FF or Safari. (Well, and who knows what happens in IE! It would be worth someone testing that, but we probably wouldn't do a bug fix for that since it has often not worked right with Sage stuff, I believe.) - kcrisman -- You received this message because you are subscribed to the Google Groups "sage-release" 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-release. For more options, visit https://groups.google.com/d/optout.
