Awesome! Huge problem in a lot of Python codebases, and hard to get around this problem without trying to go all in on type-safety. Even so, you don't get granular control like this.
Very cool..exciting to see you tackling the modular architecture challenge head-on, and also wrt to dynamically imported modules..would also be interesting to see some sort of IDE integration for real-time feedback directly in the development workflow. Would be nice to have a discord community around this!
Looks really interesting for managing modular codebases!
This is sick, it would be amazing if I could get complete backend codebase a OOTB with this, ruff, and other meta Python packages.
Hi HN! I'm one of the developers of modguard.
I'm excited to get feedback from you all, and I'm happy to answer any questions you might have!
Great idea, definitely ran into a lot of these problems at my last gig. Will try this out next time I'm working on a python project.
> specific nonstandard custom syntax to access modules/submodules such as getattr or dynamically generated namespaces will not be caught by modguard
Are any plans to get modguard to take these cases into account? I imagine this is harder without doing anything at runtime.