some terminals (like travis and jupyter) can not have colored output, because the terminal is checked again with humanfriendly.terminal_supports_colors(stream)

this leads to no coloured output on travis and jupyter.

the 'isatty' keyword is triadic :

isatty = None  # autodetect if we can use color
isatty = False  # dont  use color

at the Moment You treat isatty = True the same way like it would be None - but isatty=True should force the use of the ColoredFormatter !

If You dont like it for a reason, You also can put a new keyword like force_color but from my point of view it should not be neccessary.

However, with that patch the colored output is possible now for Jupyter (on stdout) and Travis (on stderr) !

please consider it, until then I need to host my own fork on pypi to get the wheels ....

yours sincerely

Robert

Python 2.6 is breaking the build. It is EOL since 2013-10-29 and no longer receiving security updates (or any updates) from the core Python team.

It's also little used. Here's installs from PyPI:

Source: https://pypistats.org/packages/coloredlogs

Also add python_requires to help pip, and remove redundant sudo: required: https://blog.travis-ci.com/2018-11-19-required-linux-infrastructure-migration

Detected issue

When passing the parameter isatty=True to the method coloredlogs.install() the logger does not always generate a colored output.

Conditions

I use this option because I run on windows and use a git bash terminal. Since git bash is using pipes it's not detecting the terminal correctly with sys.stdout.isatty().

Expected behavior

I would expect with the isatty=True to the method coloredlogs.install() that the colored output is forced independent of sys.stdout.isatty().

Version

This has been discovered when running on version 14.0.

More information on issue

Debugging the module has shown that the method terminal_supports_colors(stream) returns false and the use_colors gets deactivated. More debugging has shown that in there the sys.stdout.isatty() is called.
Looking at those lines there is no difference from 'isatty'=None and 'isatty'=True.

Possible fix

For me changing line 433 to if use_colors is None: solved the issue. But I cannot tell if this is a valid fix, since I do not know other use cases.

When I use selenium+phantomjs and coloredlogs, I found all log will output to the console, include selenuim's log. I just want show my log. How can I close the other logs?

This is my code:

FIELD_STYLES = dict(
    asctime=dict(color='green'),
    hostname=dict(color='magenta'),
    levelname=dict(color='green', bold=coloredlogs.CAN_USE_BOLD_FONT),
    filename=dict(color='magenta'),
    name=dict(color='blue'),
    threadName=dict(color='green')
)

LEVEL_STYLES = dict(
    debug=dict(color='green'),
    info=dict(color='cyan'),
    verbose=dict(color='blue'),
    warning=dict(color='yellow'),
    error=dict(color='red'),
    critical=dict(color='red', bold=coloredlogs.CAN_USE_BOLD_FONT)
)
logger = logging.getLogger("ProjectName")

cf = ConfigParser.ConfigParser()
cf.read("config.ini")
if cf.has_option("ProjectName", "debug") and cf.get("ProjectName", "debug") == "On":
    level = "DEBUG"
else:
    level = "INFO"

coloredlogs.install(
    level=level,
    fmt="[%(levelname)s] [(%(threadName)s)] [%(asctime)s] [%(filename)s:%(lineno)d] %(message)s",
    datefmt="%H:%M:%S",
    level_styles=LEVEL_STYLES,
    field_styles=FIELD_STYLES,
)

And I write log like this:

logger.debug("debug information")

And the output like this:

[INFO] [(MainThread)] [00:06:46] [WebSpider.py:74] initial web spider phantomjs process pool...
[DEBUG] [(MainThread)] [00:06:51] [remote_connection.py:415] POST http://127.0.0.1:11225/wd/hub/session {"requiredCapabilities": {}, "desiredCapabilities": {"javascriptEnabled": true, "phantomjs.page.settings.resourceTimeout": 10, "phantomjs.page.settings.loadImages": false, "platform": "ANY", "browserName": "phantomjs", "version": ""}}
[DEBUG] [(MainThread)] [00:06:51] [remote_connection.py:510] Finished Request
[INFO] [(MainThread)] [00:06:51] [WebSpider.py:85] 25.00% finished.

The "remote_connection.py:510" isn't my log, maybe it create by selenium or phantomjs.

After read some docs, I found the coloredlogs.install() function has a param called logger, if it None, it will set to the root logger, so I pass my logger to it, like this below:

coloredlogs.install(
    level=level,
    logger=logger,
    fmt="[%(levelname)s] [(%(threadName)s)] [%(asctime)s] [%(filename)s:%(lineno)d] %(message)s",
    datefmt="%H:%M:%S",
    level_styles=LEVEL_STYLES,
    field_styles=FIELD_STYLES,
)

But this time, there is no log output to console, so I pass a stream to this function, "stream=sys.stdout", also no output.

Did I do something wrong?

In the present version, colouring of the different fields (name, loglevel, hostname, etc.) seems to be dependent on placement of white spaces. I.e. if no white spaces are placed between fields, consecutive fields will have the colour of the first in string. Is that intended behaviour? It can be seen using the following code:

import coloredlogs, logging
from logging import debug, info, error, warning as warn
coloredlogs.install(level='DEBUG', fmt=formatstring, datefmt='%d.%m.%y %H:%M' )
debug("debug")
info("info")
warn("warn")
error("error")

where two different format strings are used (note the spaces around levelanme, name and process string formatters):

formatstring='[ %(levelname)-8s ] (%(asctime)s %(name)s @ %(hostname)s [%(process)d]'   # with spaces
formatstring='[%(levelname)-8s] (%(asctime)s %(name)s@%(hostname)s[%(process)d]'       # without spaces

The result is something like this (note the color of the levelname and the blurred hostname field):

The following example from the documentation:

import coloredlogs, logging
coloredlogs.install()
logger = logging.getLogger()
logger.info("this is an informational message")

Gives this error in python 2.7.6 on Ubuntu 14.04:

Traceback (most recent call last):
  File "./coloredlogs.py", line 21, in <module>
    import coloredlogs, logging
  File "/home/confus/misc/test/coloredlogs.py", line 22, in <module>
    coloredlogs.install()
AttributeError: 'module' object has no attribute 'install'

IIRC, a LogFilter can actually modify the LogRecord objects. Perhaps instead of (inflexibly) hard-coding the log format, you could just define a custom filter that wraps parts of the LogRecord with the proper unicode color codes?

Hello, thank you for this beautiful package :)

In version 14.0 we are facing this error:

AttributeError: module 'coloredlogs' has no attribute 'CAN_USE_BOLD_FONT'

Was this removed or something?

Includes #79, the last commit https://github.com/xolox/python-coloredlogs/commit/036faef9fde9421aabb01d6e7f48d34c6bbdc359 here is new.

Here's the pip installs for coloredlogs from PyPI for January 2020:

| category | percent | downloads | |----------|--------:|----------:| | 3.7 | 43.45% | 247,468 | | 3.6 | 34.84% | 198,447 | | null | 6.02% | 34,265 | | 2.7 | 5.87% | 33,427 | | 3.5 | 4.91% | 27,946 | | 3.8 | 4.48% | 25,516 | | 3.4 | 0.44% | 2,506 | | 2.6 | 0.00% | 7 | | 3.9 | 0.00% | 7 | | Total | | 569,589 |

Source: pip install -U pypistats && pypistats python_minor coloredlogs --last-month

Windows 10 supports ANSI by default. But right now the use of Colorama on Windows is hardcoded. terminal.terminal_supports_colors looks for the env var ANSICON maybe the same can be used for coloredlogs?

I get this error when trying to import coloredlogs into my python program. I tried the suggestions here https://stackoverflow.com/questions/32680081/importerror-after-successful-pip-installation but they didn't help

I am trying to use to logger with different levels for FileHandler (DEBUG) and StreamHandler (WARNING). However, after I set the handlers for the logger, and whether I set the level argument in coloredlog.install or not, the FileHandler debug level is overwritten with the level set in level argument in coloredlogs.install whether I set the argument or not.

import logging, coloredlogs
logger = logging.getLogger(__name__)

c_handler = logging.StreamHandler()
f_handler = logging.FileHandler("app.log", "w")

c_handler.setLevel(logging.DEBUG)
f_handler.setLevel(logging.DEBUG)

c_format = logging.Formatter('%(name)s - %(levelname)s - %(message)s')
f_format = logging.Formatter('%(asctime)s - %(name)s - %(levelname)s - %(message)s')
c_handler.setFormatter(c_format)
f_handler.setFormatter(f_format)

logger.addHandler(c_handler)
logger.addHandler(f_handler)

coloredlogs.install(level=logging.WARNING, logger=logger)

logger.debug('This is a debug message')
logger.info('This is an info message')
logger.warning('This is a warning message')
logger.error('This is an error message')
logger.critical('This is a critical message')

logger.critical("NICE MESSAGES")

Here is the output in the app.logs file:

2023-01-03 11:30:15,565 - __main__ - WARNING - This is a warning message
2023-01-03 11:30:15,566 - __main__ - ERROR - This is an error message
2023-01-03 11:30:15,567 - __main__ - CRITICAL - This is a critical message
2023-01-03 11:30:15,567 - __main__ - CRITICAL - NICE MESSAGES

You can that the file output doesn't include debug message, which I clearly have set above.

If I make a subprocess call (of any kind, Popen, run, check_call, check_output, e.t.c) it will break the coloring of every single further log.

Windows Terminal:

PyCharm:

You can see that I added test1 and test2 logs before and after the subprocess call and only test2 broke.

I have no idea why this is happening. I've also tried run() with stdout and stderr redirected to subprocess.DEVNULL, and it still happens.

The relevant line of code can be found here:

https://github.com/rlaphoenix/nton/blob/ccf9dbfcbb5ea25849733630173e96bf27062132/nton/main.py#L220

Are there any examples of changing colours? The official documentation seems to show everything as environment variables. How do you do this in code? Is it passed as a parameter to the install function similarly to fmt= ?

Warehouse now uses the project_urls provided to display links in the sidebar on this screen, as well as including them in API responses to help the automation tool find the source code for Requests.

Python 3.10 added a defaults argument to the Formatter.__init__ to enable you to use custom fields in the format string. Itʼd be nice if ColoredFormatter and coloredlogs.install supported this too.