- --color=always does not always output color (#106)
- Eliot-tree crashes with Unicode encoding errors on non-UTF8 terminals even when specifying --ascii. (#95)
The public API for render_tasks was broken unnecessarily in 19.0.0, this release replaces the colorize keyword argument and deprecates it instead.
- Tree lines are now colored to help differentiate nested tasks, action tasks that have failed are also colored distinctly; --no-color-tree will disable tree line colors. (#76)
- An alternative color theme is now provided for light themed terminals, the COLORFGBG environment variable is used to try detect this but can be set explicitly with --theme light. (#78)
- Timestamps can now be displayed in local time with --local-timezone. (#79)
- Unicode and color output is now supported on Windows. (#82)
- Colorize tree lines by default, use --no-color-tree to disable the feature. Tree lines normally cycle through several colors, however the lines of failed actions will be colored in a way that differentiates them. (#87)
- It is now possible to configure eliottree's defaults via a config file, as well as override the color theme. Use --show-default-config to create a base config. (#88)
- Passing multiple --select arguments interacted in a way that always failed. (#37)
- Added some examples of --select usage. (#37)
- #75
- Timestamps are now rendered after the action status or message level. A duration is included too when available. (#72)
- Exceptions that occur during node or value formatting no longer interrupt processing and are displayed after the tree output. (#69)
- Fixed an incompatibility with iso8601 0.1.12. (#60)
- Python 3 compatibility was improved. (#35)
- Human-readable values are now only transformed at render time instead of mutating the log data. (#39)
- The tree-format library is now used for rendering the tree and colored output was added. (#19)
- Command-line options --start and --end were introduced to allow more easily specifying a time range of messages. (#38)
- Context is now reported when JSON or Eliot parse errors occur. (#42)
- Terminal control characters in Eliot data are now converted to their innocuous Unicode control image equivalent. (#44)
- Eliot's robust builtin parser is now used to build the tree data. (#52)
- #46, #54, #56