Hi, I’m currently using this to log my python process

logging.basicConfig(filename='filename.log', level=logging.DEBUG)

logger = logging.getLogger()

sys.stderr.write = logger.error

sys.stdout.write = logger.info

And then using print(f’{datetime.now()} log message’) where I want to log.

It’s working OK, buy I would like to live it to ic, but can’t find any info on how to send the ic output to the logger.

Thanks for any help.

  • cbarrick@lemmy.worldEnglish
    4·
    9 months ago

    Overwriting sys.stdout and sys.stderr seems like a Bad Idea™.

    Browsing the icecream source code, it looks like you can do this:

    logger = logging.getLogger()
ic.configureOutput(outputFunction=logger.debug)

    And then just make sure the logger is configured to actually print at DEBUG level.

    • driving_croonerOP
      1·
      9 months ago

      Thanks, tried the next

      logging.basicConfig(filename='filename.log', level=logging.DEBUG)

logger = logging.getLogger()
ic.configureOutput(outputFunction=logger.debug)

ic('test')

      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)

      • cbarrick@lemmy.worldEnglish
        3·
        9 months ago

        Just to confirm, if you change ic('test') to logger.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 to ic, 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 with ic.

        • driving_croonerOP
          1·
          9 months ago

          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)

  • sloppy_diffuser@sh.itjust.worksEnglish
    2·
    9 months ago

    Never used ic before, but there is an example in the README on GitHub.

    >>> import logging
>>> from icecream import ic
>>>
>>> def warn(s):
>>>     logging.warning(s)
>>>
>>> ic.configureOutput(outputFunction=warn)
>>> ic('eep')
WARNING:root:ic| 'eep': 'eep'
    • driving_croonerOP
      1·
      9 months ago

      Thanks, tried the next:

      logging.basicConfig(filename='filename.log', level=logging.DEBUG)

logger = logging.getLogger()

def warn(s):
    logging.warn(s)

ic.configureOutput(outputFunction=warn)

      But it didn’t create the .log file and the ic output was printed on the screen instead of the file (that was never created anyway)

  • nxdefiant@startrek.website
    1·
    9 months ago

    If you’re talking about the package icecream, there’s “ic.format()” that returns a string you can log, instead of printing directly to standard out.

    More generically, you can have pythons logger capture all of standard out, but that’s kind of a shotgun approach, and depending on what your doing, may have some side effects you don’t want.