logging_strict

U are not wrong.

Dependency management is tough and often frustrating. Dealing with resolving dependency conflicts is unavoidable. This area is a constant focus of development, so could see improvements over time.

Some packages to keep an eye on:

pip & setuptools

pip-tools (specifically pip-compile)

https://pypi.org/project/pip-compile-multi/

poetry

Any others i've missed?

If it's worth sharing it's worth to accompany the blog post with a repo containing unittests and tox.ini and pre-commit

If that had been done, tox would give feedback that match switch support is py310+

functools.singledispatch might be helpful to test multiple implementations

Complaint about sharing code within a blog post is the quality is ALWAYS suspect.

Lets leave crapoverflow.com style code examples in the past. Instead share tested code.

Also logging is not isolated. Bleeds all over the place. Which is a deal breaker

Not worth the endless time doing forensics

Agree! Lets stick with multiprocessing

one thread sounds nice. Lets do much more of that

that's pretty cool u are curating release announcements

Just activate the venv and then put it out of your mind. Can activate it with either a relative or absolute path. Doesn't matter which