Sqlalchemy in general is great but the data class integration feels non pythonic to me, due perhaps to catering first to the typing crowd instead of the ergonomic one.
I felt that too but over time decided that it compromised the theoretical pythonicity for the practical compromise of being flexible enough to work properly with SQL.
One other reason for its popularity and success is how engaged the orginal developer is with the overall community.
This is interesting, from the PSC, as a whole: ‘Resisting soft conduct moderation when people point out problematic statements in what has been said. When someone tells you something said earlier was problematic, listen. That is not an opportunity for debate. That is an expression of pain. It is time to stop and reflect upon what has happened.’
I genuinely find the PSC’s suspension of Mr. Peters to be problematic given my current understanding of the situation. Will they listen to my expression of pain? Will they stop and reflect on their actions, and on the repercussions of those actions on Mr. Peters, the Python community and the software community as a whole?
Or will they try to exclude me, as they have exclude Mr. Peters?
If bias plus power is a problem, who here has the power: the one suspended, or the ones suspending?
Wow. I can only say I can't imagine such conversations take place in this way at my company (or most companies with a decent HR department) -- some people would be fired for that. But this is open source project, I don't know what's happening.
sort of reminds me of https://github.com/google/gvisor, re syscall interception and checking. gvisor had some significant performance impacts for io/syscall heavy workloads, but potentially seccomp/bpf could do better albeit that's mostly filtering/transform on param re more minimal touchpoint.
