A partial rewrite of the famous requests library with a better defaults and certificate handling
Project description
begs
A partial rewrite of the famous requests library with a better defaults and certificate handling
begs
is a from-scratch rewrite of the python request
library. It is API-compatible with requests
, but has some improvements.
Why you should consider using begs over requests:
- It is much lighter. While
requests
(314 KB) depends onurllib3
(660 KB),certifi
(257 KB),idna
(467 KB) andcharset-normalizer
(220 KB),begs
has no dependencies and is less than 20 KB, making it a great choice for use in packages where size matters. - The
requests
library does not support using the built-in system certificate store - relying instead on the hard-coded ssl certificates in thecertifi
library. This makes distribution to systems located behind SSL-proxy firewalls with self-signed certificates a nightmare.begs
supports the system certificate store by default, and makes appending additional certificates to the trusted CA list a breeze. - The
requests
library has a long-standing issue of allowing users to shoot themselves in the foot by not providing a default timeout.begs
has a very reasonable 30 second timeout which can be adjusted as-needed. begs
also supports various retry options, and will even automatically retry in situations where it can be determined that a retry would be safe and idempotent (such as a 503 response to a POST, or a 504 response to a GET)
Getting Started:
import begs
begs.get('http://microsoft.com')
It's that easy!
Another Example:
import begs
req = begs.post('https://webhook.site/85bd2945-c257-4fbb-bd95-0808b882a6d0', data={'foo': 'bar'}, params={'me': 'you'})
req = begs.post('https://webhook.site/85bd2945-c257-4fbb-bd95-0808b882a6d0', json={'foo': 'bar'}, params={'me': 'you'})
log.debug('here are the in-scope variables right now: %s', dir())
log.info('%s v1.2 HAS STARTED', __file__)
log.warning('here is a warning message')
log.error('generally you would use error for handled exceptions which prevent further execution')
log.critical('generally you would use critical for uncaught exceptions')
The init()
function has more optional parameters:
init(filename, to_console=True, level=DEBUG, max_kb=1024, max_files=5)
Setting to_console
to False
is useful for windowed applications such as those compiled with pyinstaller
which have no console.
The valid options for level
are DEBUG
, INFO
, WARNING
, ERROR
, and CRITICAL
in that order. setting the level to ERROR
, for example, will silence your log.debug()
and log.warning()
calls while still logging your log.error()
and log.critical()
calls.
max_kb
sets the max logfile size before the log is rotated
max_files
sets the max number of rotating logs that are to be kept before the oldest is deleted. So, for example, the default max_kb
of 1024 and max_files
of 5 means that up to 5 megabytes of logs will be kept, split among five 1MB files. Once the log reaches 5MB and 1byte, the oldest of the 5 files is rotated away, leaving four 1MB archived log files, and a 1byte active log file
There is another special type of log function that can only be used inside of an exception handler. It will log the full exception traceback for you, (as level=CRITICAL) along with any helpful comments you may have about the exception
try:
a = 1/0
except:
log.exception("You can't divide by zero!")
because nobody has time to type out complicated words like exception
or critical
, and code looks worse when the print statements are all different lengths, there is shorthand here for you.
instead of this:
import lovely_logger as log
log.init('my_log_file.log')
log.debug('This is a debug log entry')
log.info('This is a info log entry')
log.warning('This is a warning log entry')
log.error('This is a error log entry')
log.critical('This is a critical log entry')
try:
a = 1/0
except:
log.exception('This is an exception log entry')
you can write it like this:
import lovely_logger as log
log.init('my_log_file.log')
log.d('This is a debug log entry')
log.i('This is a info log entry')
log.w('This is a warning log entry')
log.e('This is a error log entry')
log.c('This is a critical log entry')
try:
a = 1/0
except:
log.x('This is an exception log entry')
By default, the logger is going to output the date/time, level, message, filename, and line number into the log file. It will print all of that same info except the date/time to the console. If you want to override what gets outputted, or change the format, you can manually set the formatting:
import lovely_logger as log
log.FILE_FORMAT = "[%(asctime)s] [%(levelname)-8s] - %(message)s (%(filename)s:%(lineno)s)"
log.CONSOLE_FORMAT = "[%(levelname)-8s] - %(message)s (%(filename)s:%(lineno)s)"
log.DATE_FORMAT = '%Y-%m-%d %H:%M:%S.uuu%z'
log.init('my_log_file.log')
log.d('This is a debug log entry')
DATE_FORMAT
follows the formatting of the built in python time.strftime() with the exception of the "uuu" which was added to support milliseconds
CONSOLE_FORMAT
and FILE_FORMAT
follow the formatting from the built in python logging library LogRecord attributes
Note that those values must be set before log.init()
is called.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.