Linux enthusiast. I code,read and stay exceptionally weird.
Subscribe to my newsletter and never miss my upcoming articles
A post or so ago, as a follow up to A Dive into Python Implementation, we had a discussion on the differences between multi-threading and multi-processing, this being a result of IronPython's feature to allow multi-threaded code to use multi-core pro...
Before we catapult command-line arguments to infinity and beyond, we should go via one more item as suggested by an avid reader, Paddy. The docopt. In case you've just popped in, here's what we have done to this moment: argv argparse getopt So far...
You read it right. It's all about implementation. Today, we will talk about the different implementations of Python. A heads up on the different kinds, be it Cpython, Brython, you name it. This in conjunction with their main advantages, in essence, o...
If you don't know about it, then you don't need it. Seriously. You don't. In the last share about The Future of the terminal, I had a rather interesting conversation with one of the readers. It sparked a thought or two.The baseline was: Most of the ...
The Unix shell; the power of text-driven commands. Simply out of this world. You can do anything with it; literally (Okay okay, you can't cook pancakes). From getting a list of last modified files, viewing files without opening them with our friends ...
As we get into more details with python command-line arguments, we have to remember the generic household name in the command line family; getopt. See, before we had the fancy argparse, we had this swiss army knife of a package. If you are a 'regula...
