My main pain point with python at work. I lpke to write shitty scripts with it, but django was a mistake (the ORM opens then close connection to db with each request)

[–] lime@feddit.nu 4 points 13 hours ago (2 children)

just run mypy dude

[–] Melusine@tarte.nuage-libre.fr 1 points 3 hours ago (1 children)

I do, and still a pain in the ass because mypy is an afterthought of python (if your models aren't in a migration then it's an error)

[–] lime@feddit.nu 1 points 3 hours ago (1 children)

is django a requirement? because fastapi works amazingly with mypy.

[–] Melusine@tarte.nuage-libre.fr 1 points 2 hours ago (1 children)

All our codebase is django and the admin is nice, and my manager is more conservative on the stack choice for the company XD

[–] lime@feddit.nu 1 points 2 hours ago

yeah that's fair. and migrating a codebase to being typed is a nightmare. it's worth it, but fixing all the little edge cases that you didn't know you had, or just boxing with the type checker when it freaks out, is an extremely frustrating experience.

[–] cmrss2@aussie.zone 1 points 9 hours ago (1 children)

Until something is Any or Unknown and everything stops working

[–] lime@feddit.nu 1 points 4 hours ago

and that's why you don't let those types in

[–] marcos@lemmy.world 3 points 12 hours ago* (last edited 12 hours ago) (1 children)

You can set a connection pool. Or use a database proxy.

EDIT: Oh, you are using Django for shell scripts?

[–] Melusine@tarte.nuage-libre.fr 1 points 3 hours ago

Yeah, but the python runtime still needs to open sockets. We have some kafka listeners using the ORM and we got the bad surprise of openning too many connection because django would keep opening them without closing them

We used it for some batch processing and to have the admin for some managing (specially for retries)