BACKWARD COMPATIBILITY:
- Remove official Python 3.5 and 3.6 support
RELEASE:
- Test on Python v3.10
- Update classifiers
- Update relevant click version
- Upgrade dev requirements
- Remove unusued pytype
BACKWARD COMPATIBILITY:
- Remove official Python 2.7 and 3.4 support [ededefb]
- Remove Elasticsearch, syslog and logz.io handlers [14f0a10]
- Change the default env var that enables file logging to
HANDLERS_FILE_PATH
[14f0a10]
ENHANCEMENTS:
- Blacken wryte.py [7f44167]
RELEASE:
- Optimize tox config and add black validation [2793d7b]
- Add pre-commit config [df03781]
- Default to Python 3.7 when building and testing.
ENHANCEMENTS:
- Add support for ec2 specific contextual fields [#27]
- Replace
datetime.now()
withdatetime.utcnow()
[33e9c11] - Optimize performance (benchmarks will come soon) [#26]
BUG FIXES:
- Reinstate k=v pair string handling only for the CLI [728a274]
This release includes many changes from different unofficial releases and is also the first official release which I feel is ready for day to day use.
- Add colored human readable ConsoleFormatter, which is used with the default stream handler.
- Support pretty-printing key=value pairs.
- Add mucho documentation.
- Allow to remove and list handlers.
- Allow to pass custom formatter.
- Add a
log
method which receives a logging level, message and objects. - Support colored console output.
- Add an
event
method which returns acid
(context id). The cid can also be passed into the event method via thecid
flag. - Add
bind
andunbind
methods for binding context to a logger. - Add
set_level
method for setting the logger's level. - Support changing log level via the
_set_level
flag incritical
anderror
log levels. - Support printing a simple message without any formatting (only the
message
field and kv pairs are printed). - Support passing kwarg type context to all logging methods (i.e.
wryter.error('Message', k=v)
. - Add OOB support (with optional dependencies) for Elasticsearch, Logzio, Syslog and File handlers.
- Expose handler configuration via env vars.
- Add many tests
- Add codeclimate checks
- Try to avoid exceptions in the logger as much as possible. Instead, display errors or exceptions in the console.
See the docs for more info.
- Initial implementation
- Make basic logger log a standard log message.
- Add a basic CLI for the development process and for user testing.
- Use Click for CLI which should be removed later to remove overhead.
- Support JSON output.
- Support Pretty Printing JSON.
- Allow to pass logger name
- Allow to pass logger level
- Allow to pass hostname
- Auto-add base fields to each JSON message:
hostname
,name
,pid
,timestamp
,level
.