Re:Python at Scale: Strict Modules
by heavenlyblue on Sunday October 20, 2019 @04:58PM
(#21307092)
Every time I hear a comment alike parent's, it makes me think how many times a day I actually read a comment in the same fashion, but about something I actually know nothing about.
What's worse is how many people blindly upvote negativity. It's still somehow cool to shit on things...
With credit to the original poster, they might be complaining about the fact that Django is a monolithic framework and you can't really use Django code without spinning up the i/o portion. Which is legitimate criticism, but frankly if that's what you need then you shouldn't be using Django.
Re:Python at Scale: Strict Modules
by heavenlyblue on Sunday October 20, 2019 @07:05PM
(#21307939)
If by I/O you mean web i/o then Django provides a perfectly functional management utility interface accessible through cli.
If, however by i/o you mean the database portion of it then Django works without database configuration, too.
Without calling setup, you cannot import anything that touches Django models, like constants defined in a file that transitively imports a Django model.
In practice, this means that any script that depends indirectly on Django code will incur a lengthy startup cost (from having to call setup()), and will fail to run if there's no database connection, even if the script itself doesn't need the db.
Re:Python at Scale: Strict Modules
by heavenlyblue on Sunday October 20, 2019 @07:09PM
(#21307959)
You can import Django models before calling setup, you will simply not be able to use the database before calling setup.
Django _does_ have a "setup" function. You can't import and use Django database connections outside of a running application without it.
Flask also has a "run" method and does no i/o without it.