-
-
Notifications
You must be signed in to change notification settings - Fork 166
report object name upon mangle_docstrings exception #164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Does this automatically integrate with sphinx logging? (that warnings are printed, and their verbose option). Maybe we can do |
done, though that prefixing is redundant with registering the logger to the
file
…On 12 Apr 2018 9:34 pm, "Joris Van den Bossche" ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In numpydoc/numpydoc.py
<#164 (comment)>:
> - builder=app.builder)
- if sys.version_info[0] >= 3:
- doc = str(doc)
- else:
- doc = unicode(doc)
- lines[:] = doc.split(u_NL)
+ try:
+ doc = get_doc_object(obj, what, u_NL.join(lines), config=cfg,
+ builder=app.builder)
+ if sys.version_info[0] >= 3:
+ doc = str(doc)
+ else:
+ doc = unicode(doc)
+ lines[:] = doc.split(u_NL)
+ except:
+ logger.error('While processing numpydoc for %r', name)
Suggestion: add [numpydoc] at the front of the message? That's also how
sphinx extensions like autodoc/autosummary do it
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#164 (review)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAEz67aRoIUL8UixRbs6O9mgyfZjgrrlks5tnzvSgaJpZM4TNYTY>
.
|
Hmm, yes, it seems they only do the [] for debug messages (and some info), and use the location for warnings and errors (at least it looks not fully consistent for somebody who is not familiar with it) |
9a5e204
to
c45bdd7
Compare
|
I tested this locally, LGTM. +1 for merging when CI issue is resolved. |
9e831d5
to
0ebfefe
Compare
1.6.5 is now 1.5 years old, should be enough. sphinx.util.logging is not present in 1.2.3, was introduced in 1.6.0;
0ebfefe
to
a29e8c3
Compare
Updated the tested Sphinx versions from |
No description provided.