/explore
|
You are here 
|
blog.hakril.net | ||
| | | | |
tenthousandmeters.com
|
|
| | | | | We started this series with an overview of the CPython VM. We learned that to run a Python program, CPython first compiles it to bytecode, and we... | |
| | | | |
jakevdp.github.io
|
|
| | | | | [AI summary] A developer demonstrates how to use ctypes to expose and access Python 3.6's internal private dictionary version number for optimization experiments. | |
| | | | |
nikhilism.com
|
|
| | | | | [AI summary] A technical post explaining how Dropbox engineers reverse-engineered CPython's internal memory structures to implement robust Python stack tracing within their out-of-process crash reporting tool, Crashpad. | |
| | | | |
dusty.phillips.codes
|
|
| | | I really appreciate Python's pathlib module for managing filesystem stuff. While I don't love the argparse module for command line parsing, I don't think it's worse than other available options. I usually choose it for my CLI scripts, since nothing else is good enough to overcome the inertia of using a third party library. Not many people seem to be aware that the two can very easily be combined such that argparse will return Path objects instead of strings that need to be adapted after you query them: | ||
