nessita

> Is this still active? Yes, it is still active, I need to "seat" with this PR to provide an answer to the author. Would you like to provide a...

Hello @keerthivasansa! Thank you so much for your patience. I'm now back at reviewing this work. I have started catching up with our previous conversations (because in all honestly, I...

Hello @gabn88! This PR is not showing in the Django "PR pending review" list because the corresponding ticket hasn't been updated. The proper procedure to get a re-review is described...

@ngnpope Hi! Would you have any availability to pick this up? A rebase onto main would be necessary and applying the latest comment about inverting the docs. /remind me about...

@ngnpope Hey there, shall we close this PR or shall we try to push it forward? Let me know, thanks! /remind me to close this if no reply in two...

Closed due to inactivity.

@VaarunSinha @Atem18 I don't think this is fixed in latest Django, this is still an issue in `main` so if anyone wants to to pick this up, please assign the...

@ngnpope Hey there, we have a new release in a week (5.1 beta release), would you have some time to re-review this PR before then to consider merging this work...

> TL;DR: This is good to go as the filename problem existed before switching to `pyproject.toml` anyway. You have two options - pin to `setuptools>=61.0.0,

> > One question though: from my experiments, we need `setuptools v63.9.0 introduced the changes that affected the filename, so I think the bounds I gave were correct? (It's what...