In addition to great Python HTTP client tools such as Requests and HTTPX, the standard library itself supplies the necessary ingredients to make a working HTTP client for API calls. This tutorial shares how to construct and customize such a tool for your own scripts.
In this article, I offer an approach for managing dotfiles in a modular fashion. I find a modular approach important because only some config files are useful in all contexts, while others are unique to a specific environment. For instance, my text editor configuration (.vimrc, in my case) is used on my Windows laptop, Linux laptop, FreeBSD server, and even my phone. On the other hand, files for configuring a Linux graphical environment, a developer’s Macbook, Windows Subsystem for Linux (WSL), or Windows Powershell, may not make sense to clutter or confuse environments to which they do not apply.
With such an abundance of freely available online resources, it is no wonder Python attracts self-taught programmers. Many well-written tutorials and even books are able to be accessed without a fee.
Books are great. Sometimes, though, I want something less heavy and more casual. Such as a tutorial.
Python tutorials abound. Sometimes, though, I want to feel like I am reading a consolidated and comprehensive volume of information about Python. In other words, a book.
Once upon a time, the Windows command line was CMD, and it was horrible. No longer.