Ülgen Sarıkavak
Ülgen Sarıkavak
> Just got word from our performance team, performance issues like n+1 actually don't count towards any quota. @sentrivana Thank you. This is good to know, but I believe my...
@auvipy Anything needed for moving further with this PR?
How is this completed?
@MestreLion Thanks for the update. Any chance you can re-close the issue as "won't be done", so anybody somehow checking this issue won't be misled.
@Nusnus Thank you. To clarify, this PR doesn't serve to the deprecation of 3.9 - it cleans residues from
I'll ask for a rebase from the latest main (not a merge in) and resolution of conflicts. Other than that, looks awesome.
@aNsHuL5217 Thank you. Adding my approval, considering the PR will be squash merged. Adding the mergers team for review.
> I think djangoproject.com should lead by example Yes, but I don't think that best practice applies to this project. One important point is that this repo is a project,...
Also, it's not clear how long we will be able to keep this project up to date with the latest version of Django, due to Python compatibility issues with Trac....
I don't disagree with the intention, but I still don't think it's needed or beneficial. We can always create a new branch with a new Django version (or main) and...