search

chrisjsewell / ipypublish

A workflow for creating and editing publication ready scientific reports and presentations, from one or more Jupyter Notebooks, without leaving the browser!
http://ipypublish.readthedocs.io
BSD 3-Clause "New" or "Revised" License
224 stars 37 forks source link

DEBUG messages during conversion #141

Open parmentelat opened 4 years ago

parmentelat commented 4 years ago

this is a question, so neither a bug report nor a feature request

I'm using ipypublish together with jupytext in the context of readthedocs

right now I am getting tons of very low-level DEBUG messages in the rtd Build details a sample full build report is https://readthedocs.org/projects/ue12-python-numerique/builds/11855478/ as I suspect you may have no access - here's a short sample

reading sources... [  5%] 0-02-outils
ipypublish: converting /home/docs/checkouts/readthedocs.org/user_builds/ue12-python-numerique/checkouts/latest/notebooks/0-02-outils.md
INFO:ipypublish:started ipypublish v0.10.12 at Thu Sep 10 21:42:25 2020
INFO:ipypublish:logging to: /home/docs/checkouts/readthedocs.org/user_builds/ue12-python-numerique/checkouts/latest/notebooks/0-02-outils.nbpub.log
INFO:ipypublish:running for ipynb(s) at: /home/docs/checkouts/readthedocs.org/user_builds/ue12-python-numerique/checkouts/latest/notebooks/0-02-outils.md
INFO:ipypublish:with conversion configuration: sphinx_ipypublish_all.ext.custom
INFO:ipypublish:running pre-conversion with: <module 'jupytext.jupytext' from '/home/docs/checkouts/readthedocs.org/user_builds/ue12-python-numerique/envs/latest/lib/python3.7/site-packages/jupytext/jupytext.py'>
DEBUG:markdown_it.rules_block.code:entering code: StateBlock(line=15,level=0,tokens=1), 15, 1397, False
DEBUG:markdown_it.rules_block.fence:entering fence: StateBlock(line=15,level=0,tokens=1), 15, 1397, False
DEBUG:markdown_it.rules_block.blockquote:entering blockquote: StateBlock(line=15,level=0,tokens=1), 15, 1397, False
DEBUG:markdown_it.rules_block.hr:entering hr: StateBlock(line=15,level=0,tokens=1), 15, 1397, False

and it goes on like that for miles ..

I can't remember exactly when this started to happen, probably a couple months back and sorry for being so dumb, but I can't either remember whether I did something specific to get these messages (and it might be so, when the build is broken it helps to pinpoint the problem); I did scrub my repo and came up with nothing, but I can't be positive that I have nothing to do with this

regardless, my question is simple, how can I set the logging level to INFO and up, so as to get more reasonable build logs ?

thanks !

chrisjsewell commented 4 years ago

Oh I know exactly when it will have happened; when I added https://github.com/ExecutableBookProject/markdown-it-py to jupytext 😉. Hmm, thats weird; the logger is already set up to only log INFO: https://github.com/chrisjsewell/ipypublish/blob/53fa92c4c7f18e36d8a9790b10de27219882f4e4/ipypublish/convert/main.py#L297 But perhaps these are getting through because the root logger is set to DEBUG (this should not be propagated though): https://github.com/chrisjsewell/ipypublish/blob/53fa92c4c7f18e36d8a9790b10de27219882f4e4/ipypublish/convert/main.py#L292

Its weird that this hasn't been an issue for any other package; I'm not doing anything crazy in markdown-it-py, just:

import logging
LOGGER = logging.getLogger(__name__)
LOGGER.debug("entering hr: %s, %s, %s, %s", state, startLine, endLine, silent)