Its been four years since I last wrote an article on this blog. Even though the domain has been active, the content has been lying dormant for a while. To take a positive spin out of this ongoing pandemic, I promised myself to revive this blog and resurrect the old content for everyone’s pleasure.
Albeit, there’ll be some articles that still needs formatting based on the new layout, but hold your breath, those changes are coming thick and fast.
The Python mock library has largely been a black hole when it comes to efficiently unit testing a Python code. Hopefully, this article will help you understand the essential bits to bump up that test coverage.
Whether it is about mocking an object, class, method or a function, in Python, everything can be more or less decomposed into a handful of similar steps. Throughout the article, we would only make use of the patch decorator that can be imported as,
Raymond Hettinger is a Python Core developer and has an amazing knack of explaining concepts related to Python in a succint manner. His talk at PyCon US 2015, titled “Beyond PEP8” revolves around the hazards of the PEP 8 style guide and learn what really matters for creating beautiful intelligible code.
Over the weekend, I pushed out a new update to the Atomize IO app and this post is all about, explaining how those numbers are calculated.
If you are unfamiliar with Atomize IO, then make sure you checkout the web app and run it against your website. I have been massively impressed with the idea behind Atomic CSS and always wanted to build something to find out, how much duplicate CSS declarations live inside the CSS codebase of popular websites and by how much they can benefit by adopting the Atomic CSS methodology.