@sethmlarson I think the onboarding process will configure each project team that way. I'd be happy to make you an admin on the playground repo to check my work.
The biggest pain point in this regard is not being able to automate it. Though I haven't looked all that hard yet.
Oy! Today, it's the 10 year anniversary for #Django PR#2692 🥳
It's definitely worth celebrating how the good forces were victorious against all the loud mouth conservatives/trolls. Since my office is full today, I might need to get both a primary cake and a replica cake for redundancy 🍰
Congrats and thanks to @fcurella and everyone else involved in this.
Starting to get warmer ☀️ hopefully the plants will stop breeding now, and my nose will stop running. I love spring and all, but months of mild hay-fever is really boring.
I’m sure I never had this when I was younger. (Maybe I just didn’t notice 🤔)
I wouldn’t normally post something personal like this, but I feel compelled to.
It seems my mother-in-law’s cancer may have taken a turn for the worse. She had to be hospitalized last night and it doesn’t look great. It’s reminding me a lot of when my mom passed from her cancer a couple of years ago, where there’s a line that is crossed — before crossing it seems like the progress is up and down, better and worse. But once that line’s crossed it’s all down from here.
I have a custom django model field in an installable standalone app.
This app has a migration file that creates a new composite type in a postgres db (if it doesn't already exist). Users installing the app shouldn't have to manually run this migration.
Anyone know how I tell django's migrations autodetector that if another app's model uses my custom model field and we generate migrations model, it needs to add a dependency to the migration associated with the custom field? 🤔
@jack I suspect you'd need to do something in MigrationAutodetector.detect_changes method similar to the generate* methods. The dependencies get associated with the operation itself as far as I can see.
Wrote a cursed custom Django field, OPField, that stores the location to a 1Password item using their custom URI (op://…) and has the ability to get the secret via the op cli.
op_uri, secret = OPField.with_secret()
I blame @CodenameTim and his blog post about the RegisterField that I haven’t been able to get out of my head since he wrote it months ago.
@bmispelon 🤩 this functionality is something that belongs in the ORM ideally. I think a third party library is a good starting point, but I'd vote for it to go straight to main. People frequently want to fetch a list of discussion threads and the latest post of each thread. Your idea is perfect for that scenario!