> So much existing multithreaded Python code is written in an unsafe manner. Even multi-process Python code is often broken. The "recommended" way to serve a D

> So much existing multithreaded Python code is written in an unsafe manner. Even multi-process Python code is often broken. The "recommended" way to serve a Django app is to run multiple workers (processes) using gunicorn. If you point the default logs to a file, even with log rotation enabled, all workers will keep stepping over each other because nobody knows which file to use. Keep in mind that this is broken by default, and this is the recommended way to use all this.