dephell VS import-linter

I've found https://github.com/dephell/dephell but seems to be outdated.

I had a few relatively famous projects (like dephell), and at some point I lost my sleep because I was "fixing bugs" in it in my head in the middle of the night. Archiving it, closing issues in everything else, and starting to just write projects for my own fun only was the best decision I ever made. Don't make my mistakes. Don't ask random people on the internet what you should do. Do what you want to do and enjoy doing.

You jest and yet...

https://github.com/dephell/dephell

Dephell is a converter for python packaging systems. It can turn poetry files into requirements.txt, or setuptools' setup.py into pipenv's Pipfile etc.

Python Packaging: There is More Than One Way to Do It

Not necessarily. You can use Dephell (https://github.com/dephell/dephell) to convert from poetry to the old-fashioned requirements.txt

(& also come across DepHell)

Never heard of https://import-linter.readthedocs.io/ before. Not sure if I like this type of solution, but it's interesting, and certainly the problem is real.

Before clicking on this, I expected to see import-linter [0] which achieves something very similar but with, in my opinion, a bit less magic. Another solution in a similar spirit is Pants [1], though this is actually a build system which allows you to constrain dependencies between different artifacts (e.g. which modules are allowed to depend on which modules).

To Sourcery's credit, their product looks much more in the realm of "developer experience" -- closer to Copilot (or what I understand of it) than to import-linter. Props to them for at least having a page about security [2] and building a solution which doesn't inherently require all of your source code to be shared with a vendor's server.

[0] https://github.com/seddonym/import-linter

[1] https://www.pantsbuild.org/

[2] https://docs.sourcery.ai/Product/Permissions-and-Security/

import-linter on GitHub