django 5.2 compatibility #495
Conversation
|
I don't think test failures are related to this change and are probably pre-existing problems with CI test configuration. |
Maybe not, some table is not created but I can't quickly understand why. |
nosnilmot
force-pushed
the
django-5.2
branch
3 times, most recently
from
9360a7a to
b02ac4b
Compare
update tests to include Python 3.13 and use by default; and drop Python 3.7 (no longer supported, incompatible with latest pytest) require pytest-django 4.11.1 to address DB access issues in 4.11.0 ensure same version of pytest & pytest-django used for local tests and CI
The problem was introduced by I've fixed that, and taken the liberty to add Python 3.13 to supported versions (and removed 3.7 as unsupported and incompatible with latest pytest/pytest-django) |
|
Oh, thanks a lot. |
|
@Suor thanks for merging this, is there a planned date for a new |
|
I usually let code to cool a little while before releasing it, but I was thinking about releasing soon. |
|
Ok, released 7.2 |
Closes #494