Debug messages are still displayed after upgrade
See original GitHub issueDescribe the bug
Debug messages are displayed throughout the program. I looked for an environment variable that maybe I had set and couldn’t find anything. Then I looked over the program and found where the logger was set. I believe that changing DEBUG
to ERROR
(if that’s another logging level in Python) will fix it.
Also, unsure if this was intentional or not
Editing to say that I wouldn’t made a pull request, but I didn’t think that changing a single word was worth doing that
How to reproduce Install to the newest version and run any command
Expected behavior Debug messages are on nearly every line
DEBUG:pipx.main:2022-01-30 22:39:38
DEBUG:pipx.main:/home/lucas/.local/share/pyenv/versions/3.10.0/bin/pipx list
INFO:pipx.main:pipx version is 1.0.0
INFO:pipx.main:Default python interpreter is '/home/lucas/.local/share/pyenv/versions/3.10.0/bin/python'
INFO:pipx.shared_libs:Time since last upgrade of shared libs, in seconds: 739. Upgrade will be run by pipx if greater than 25920
How to fix
Change the line in main.py
which says:
# from
"loggers": {"pipx": {"handlers": ["stream", "file"], "level": "DEBUG"}},)
# to
"loggers": {"pipx": {"handlers": ["stream", "file"], "level": "ERROR"}},)
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Debug console doesn't show messages after upgrading ...
go to Android Monitar tab. · and set option to No filters at top ,right side of the tab. · and then start...
Read more >Important Information on Debug Commands - Cisco
To Stop Debugging ... To stop a debug, use the no debug all or undebug all commands. Verify that the debugs have been...
Read more >Console app not showing info and debug logs
I've tried running the Console app as root, via sudo from the command line and the same issue occurs; no debug or info...
Read more >Write-Debug (Microsoft.PowerShell.Utility) - Microsoft Learn
By default, debug messages are not displayed in the console, but you can display them by using the Debug parameter or the $DebugPreference...
Read more >Debugging Best Practices - ServiceNow Developers
Currently, in the Service Portal interface, the section for Debug Output does not appear at the bottom of the content frame and therefore,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Here is some information:
It was any
pipx
command that would display debugging messages.pipx list
,pipx install
, etc. After I went to$PYENV_ROOT/versions/3.10.0/lib/python3.10/site-packages/pipx
and changed that line, the debugging messages seemed to disappear.I was unsure if this was a
pipx
problem or not. I thought that it was since I had only noticed the debugging messages when usingpipx
and they seemed to stop after changing that line. However, after I filed this bug, I noticed that there was another Python program displaying debugging messages, though I cannot remember which one it was.The issue started after upgrading
pipx
. I cannot remember if I upgraded it just because or if it was whenever I switched my Python version from 3.9.5 to 3.10.0 usingpyenv
.I checked to see whether the logging framework with Python used some sort of environment variable and couldn’t find anything. I went through some of the environment variables that I had set to see if I could maybe find something and couldn’t find anything either. I just went and modified the file as mentioned above and changed it back from
ERROR
toDEBUG
and the messages started showing again.Here it is in action
I downgraded pipx to
0.17.0
and the same thing is going on. Whenever I change it fromDEBUG
toERROR
the messages go away. Once my mac laptop gets done upgrading I’m going to try the same thing on there and see if I have the same issues.Do you know of any sort of environment variable that this could be reading from? I’m not really sure of anything else, unless
pyenv
orpython
was compiled with some sort of flag that enables persistent debuggingAlso switched from python
3.10.0
to3.9.5
and installedpipx
version1.0.0
and see debugging messagesEdit: That my mac laptop does not seem to have this issue either.
I just find it odd how I can change one word in a file to stop the debug messages from being displayed, but I am unsure if it is
pipx
that is actually causing this to be the case. I guess after you see this message, if you feel like closing this issue you can. If there is anything that I figure out, I will come back here and post it