Some related work from the same people, around how they sped up their AST analysis [0]. It looks like they have a few tools that would be very useful for wrangling existing python codebases and getting them under control.
[0] https://www.gauge.sh/blog/python-extensions-should-be-lazy
In TypeScript land, module boundaries currently enforceable using eslint with nx rules: https://nx.dev/nx-api/eslint-plugin/documents/enforce-module...
Yet another tool that makes it harder to sync my projects and do ad-hoc coding on my phone, or anywhere else that I can't setup the Rust toolchain. That's all I'm seeing with this rustification of the Python ecosystem: a reduction in the breadth of practically supported targets for the language.
Looks interesting, but I'm having a hard time understanding what this does that isn't covered by the ruff rules checking for uses of private functions or classes.
It seems you can define an extra level of who's allowed to import what...but why would I want to add that on top rather than using standard conventions? Why would I want to let foo import baz, but not let bar import baz?