I've been mostly pleased with our use of python-polylith [1] with poetry in a production application. We output a webapp, python sdk, and CLI as separate "proje

I've been mostly pleased with our use of python-polylith [1] with poetry in a production application. We output a webapp, python sdk, and CLI as separate "projects." It doesn't _really_ solve python dependency/import issues. Instead, it helps to you keep your project in discrete chunks and well-organized. It also makes it easy to package up the separate projects as artifacts. I've run into some issues with versioning separate projects but I suspect that is a matter of bandwidth rather than an actual, insoluble issue. I'd use it again at a startup or on project where you need to ship a bunch of artifacts but don't have a lot of bandwidth. [1] https://github.com/DavidVujic/python-polylith https://github.com/DavidVujic/python-polylith