Support for pylint 4.0+

[Pierre-Sassoulas]

Refs #467, blocked by #472

[coveralls]

Pull Request Test Coverage Report for Build 19191889690

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-85.3%) to 0.0%

---

Totals
Change from base Build 19189660637:	-85.3%
Covered Lines:	0
Relevant Lines:	0

---

💛 - Coveralls

[coveralls]

Pull Request Test Coverage Report for Build 18467157949

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-85.3%) to 0.0%

---

Totals
Change from base Build 17751474096:	-85.3%
Covered Lines:	0
Relevant Lines:	0

---

💛 - Coveralls

[coveralls]

Pull Request Test Coverage Report for Build 18467157949

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-85.3%) to 0.0%

---

Totals
Change from base Build 17751474096:	-85.3%
Covered Lines:	0
Relevant Lines:	0

---

💛 - Coveralls

[Pierre-Sassoulas]

Blocked by python 3.13 (#440) / python 3.14 support.

[mspiller]

Django 5.1 is still officially supported till EOY and shouldn't be removed.

[Pierre-Sassoulas]

@mspiller is there any reason not to use 5.2 instead ?

[mspiller]

Well 5.1 is still supported and will be till end of the year. Having tooling that does not support officially maintained versioned is a PITA. For example we managed to migrate one of the projects from 5.1 to 5.2 just yesterday.

And before you ask :D Yes development libs are updated more often than runtime env like Django that needs lots of testing before going to prod.

[Pierre-Sassoulas]

Sure (I put back 5.1), but I was just wondering as it's a minor version upgrading should be uneventful ? (as even upgrading a django major is uneventful in my experience)