You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Goal
We're on our way upgrading a codebase from an old Django to the latest LTS. We're currently on Python 3.7 and it will be complicated to change both python and django at the same time
Problem
As far as the metadata tell
In 7.10.0, the lib was compatible with py3.7 but not with django 3.2
In 7.10.1, the lib was not (officially) compatible with py3.7, but was compatible with django 3.2
That said, I'm inclined to think it's an error in the metadata, because, for example, this commit added compatibility to django 4.0 while python 3.7 was still supported, and it's strange that the lib would be compatible with django 3.1 and 4.0 and not 3.2.
I think I can try to find what gives exactly, but if you already know the issue and you can tell from the top of your head what version we can target to have both py3.7 and django3.2 without it beeing a hassle, you can save me a headache :)
(I'd be inclined to take 7.10.0 as the last version that officially supported py3.7 and assume it supported dj3.2, even though it looks like nothing was changed in subsequent commits that would likely make later versions fail with py3.7)
Yeah, I see 3.2 was added to the test suite in 038026c so 7.7.1, so that 99% answers the question. If you can just confirm that it was a small metadata issue and not a bigger problem, I won't bother you anymore :)
Repository owner locked and limited conversation to collaborators on Jan 5, 2023
Activity
ewjoachim commentedon Jan 5, 2023
Yeah, I see 3.2 was added to the test suite in 038026c so 7.7.1, so that 99% answers the question. If you can just confirm that it was a small metadata issue and not a bigger problem, I won't bother you anymore :)