/explore
|
You are here 
|
felsqualle.com | ||
| | | | |
blog.zgp.org
[AI summary] The author tests a website's crawling behavior by observing how three different IP addresses access a specific game ruleset page, questioning the reasons behind the multiple crawlers. |
|
| | | | | ||
| | | | |
kevquirk.com
Peter digs into why his server was suddenly overloaded and finds a swarm of bots chewing through his blog. |
|
| | | | | ||
| | | | |
ruk.ca
|
|
| | | | | ||
| | | | |
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: |
|
| | | |||
