Search Results for "call log"

After building hundreds of open source software I've ended up inventing a git commit log standard called EMOJI-LOG that helps me understand a project's history with a less cognitive load just by looking at the git log. I like emoji. I like ’em a lot. Programming, code, geeks/nerds, open-source, all of that is inherently dull and sometimes boring. Emoji (which is, in fact, the plural of emoji) helps me add colors and emotions to the mix. Nothing wrong if you want to attach feelings to this 2D...

Autologging eliminates boilerplate logging setup code and tracing code, and provides a means to separate application logging from program flow and data tracing. Autologging provides two decorators and a custom log level: "autologging.logged" decorates a class to create a __log member. By default, the logger is named for the class's containing module and name (e.g. "my.module.ClassName"). "autologging.traced" decorates a class to provide automatic CALL/RETURN tracing for all class, static, and instance methods, as well as the special __init__ method (by default) "autologging.TRACE" is a custom log level (lower than logging.DEBUG) that is registered with the Python logging module when autologging is imported

...Most importantly, it's taking the measurements on actual page loads, so the data has the potential to be much more valuable than in vitro measurements. Modern browsers log a bunch of page performance data, Bucky includes a method for writing all of this in one go. It won't do anything on browsers that don't support the performance.timing API. Call it whenever; it will bind an event if the data isn't ready yet.