this post was submitted on 25 Mar 2024
11 points (100.0% liked)
Python
6394 readers
9 users here now
Welcome to the Python community on the programming.dev Lemmy instance!
📅 Events
Past
November 2023
- PyCon Ireland 2023, 11-12th
- PyData Tel Aviv 2023 14th
October 2023
- PyConES Canarias 2023, 6-8th
- DjangoCon US 2023, 16-20th (!django 💬)
July 2023
- PyDelhi Meetup, 2nd
- PyCon Israel, 4-5th
- DFW Pythoneers, 6th
- Django Girls Abraka, 6-7th
- SciPy 2023 10-16th, Austin
- IndyPy, 11th
- Leipzig Python User Group, 11th
- Austin Python, 12th
- EuroPython 2023, 17-23rd
- Austin Python: Evening of Coding, 18th
- PyHEP.dev 2023 - "Python in HEP" Developer's Workshop, 25th
August 2023
- PyLadies Dublin, 15th
- EuroSciPy 2023, 14-18th
September 2023
- PyData Amsterdam, 14-16th
- PyCon UK, 22nd - 25th
🐍 Python project:
- Python
- Documentation
- News & Blog
- Python Planet blog aggregator
💓 Python Community:
- #python IRC for general questions
- #python-dev IRC for CPython developers
- PySlackers Slack channel
- Python Discord server
- Python Weekly newsletters
- Mailing lists
- Forum
✨ Python Ecosystem:
🌌 Fediverse
Communities
- #python on Mastodon
- c/django on programming.dev
- c/pythorhead on lemmy.dbzer0.com
Projects
- Pythörhead: a Python library for interacting with Lemmy
- Plemmy: a Python package for accessing the Lemmy API
- pylemmy pylemmy enables simple access to Lemmy's API with Python
- mastodon.py, a Python wrapper for the Mastodon API
Feeds
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Overwriting
sys.stdout
andsys.stderr
seems like a Bad Idea™.Browsing the icecream source code, it looks like you can do this:
And then just make sure the logger is configured to actually print at DEBUG level.
Thanks, tried the next
But didn't create the log file and the output was printed on the screen and not on log file(that was never created anyway)
Just to confirm, if you change
ic('test')
tologger.debug('test')
it works as expected? I.e. it creates the log file?Edit: Also if you change the output format of the logger and use it as the
outputFunction
toic
, does it include the customized format?I just want to confirm if your
ic
is routing through the logger or not, to know if it's a problem with your logging config or withic
.EDIT: I think I had something wrong on the logging.basicConfig() because now is creating the .log file when running that line and then the ic() is writing correctly on the log file.
Edit 2: I found what was happening, I was using another directory and now found the og log file with all the tests that were supposed lost.
Thanks for your help.
logger.debug('test') created the log file and logged test, after that ic('test') wrote correctly on the log file.
Restating the kernel and running again directly with ic('test') it wrote on the already existing log file.
So, to recap. If the .log file doesn't exists, ic() didn't create the file and nothing is logged, if the the log file already exists, then the ic() wrote correctly on the log file.
The only missing part is how to create the log file without needing of the logger.debub('').
Tried to create an empty log file with open('logfile.log', 'a').close() and the log file is created but is useless (dosen't even write the logger.debug('test') output)