bausgwi678
The default for multiprocessing is still to fork (fortunately changing in 3.14), which means all of your parent process’ threaded code (incl. third party libraries) has to be fork-safe. There’s no static analysis checks for this.
This kind of easy to use but incredibly hard to use safely library has made python for long running production services incredibly painful in my experience.
[1] Some arguments to subprocess.popen look handy but actually cause python interpreter code to be executed after the fork and before the execve, which has caused production logging-related deadlocks for me. The original author was very bright but didn’t notice the footgun.
If you live somewhere which is significantly colder outside than in (e.g. 0-5C out, 21C inside) heating outside air to comfortable temperatures will greatly decrease humidity. Couple this with a system which circulates air, or even exchanges inside&outside air and you will have incredibly low humidity inside.
I live somewhere which often sees 10-15C @ 80% humidity over winter, and the only air circulation in my house is from opening doors/windows. 70% internal humidity @21C is incredibly common. It takes a bit of moisture management to keep it below 60%.