Skip to content
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

pythonrc log spam #67

Open
gabriel-v opened this issue Feb 7, 2023 · 1 comment
Open

pythonrc log spam #67

gabriel-v opened this issue Feb 7, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@gabriel-v
Copy link

The pythonrc logs with print() things like HTTP fetches.

Once you start polling HTTP endpoints every few seconds, logs get very spammy very fast. The main culprit was the message 849: fopen: fetching

On my fork I changed some print statements into DBG: fork commit

I also used the logging library to allow me to bring back the spam by doing logging.getLogger(None).setLevel('DEBUG').

Questions:

  • do you want to use the logging library in pygbagrc for log control, or do you want to keep that if PyConfig.dev_mode?
  • what is the good way to set PyConfig.dev_mode = True | False to control logging?
@pmp-p pmp-p added the enhancement New feature or request label Feb 7, 2023
@pmp-p
Copy link
Member

pmp-p commented Feb 7, 2023

i'll do the same remark i did for lvgl micropython. I want people to be able to see what is getting in/out from their browser. Maybe an acceptable compromise would be to delay/drop more and more after hitting the same url with no error status.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants