Ignore all exceptions in ._sage_doc_ attribute access

[jdemeyer]

The current docbuilder cannot cope with obj._sage_doc_ accesses raising RuntimeError for example.

Component: documentation

Author: Jeroen Demeyer

Branch/Commit: c9980ee

Reviewer: François Bissey, Karl-Dieter Crisman

Issue created by migration from https://trac.sagemath.org/ticket/19671

[jdemeyer]

Description changed:

--- 
+++ 
@@ -1 +1 @@
-The current docbuilder cannot cope with `_sage_obj_()` calls returning `RuntimeError`.
+The current docbuilder cannot cope with `obj._sage_obj_` accesses raising `RuntimeError` for example.

[jdemeyer]

Branch: u/jdemeyer/fix_docbuild_for_sagenb_upgrade

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:

c9980ee

Allow all exceptions in obj._sage_obj_

[sagetrac-git]

Commit: c9980ee

[jdemeyer]

Description changed:

--- 
+++ 
@@ -1 +1 @@
-The current docbuilder cannot cope with `obj._sage_obj_` accesses raising `RuntimeError` for example.
+The current docbuilder cannot cope with `obj._sage_doc_` accesses raising `RuntimeError` for example.

[kcrisman]

comment:6

Ah, I see now why Sloane.

As I said in #19616, it does build doc successfully with these changes, though I don't have my Sage install convenient to actually try the tests. Anyone else could review that.

[jdemeyer]

comment:7

Replying to @kcrisman:

try the tests.

You mean doctests or something else? The doctests pass.

[kcrisman]

comment:8

I mean doctests, but I didn't know if one was allowed to use the patchbot to confirm this or test it oneself. I usually try them 'by hand' and a few other things, and I won't be able to do more with that until at least Monday, probably Wednesday. If you think this is sufficient though then I certainly trust patchbot + you and you can set it to positive review.