Update version compatibility metadata #2954
Conversation
|
Ah, Renovate didn't change Python versions used in test matrix, will update that as well |
sobolevn
left a comment
sobolevn
left a comment
There was a problem hiding this comment.
I would put it like this. Because now we already have some parts of 6.0 and we can't claim to support 5.2, because it will allow code that does not work on 5.2 :(
But, some more work is required to support 6.0 to claim it
|
|
||
| | django-stubs | Mypy version | Django version | Django partial support | Python version | | ||
| |----------------|--------------|----------------|------------------------|----------------| | ||
| | (unreleased) | 1.13 - 1.19 | 5.2 | 6.0, 5.1, 5.0 | 3.10 - 3.14 | |
There was a problem hiding this comment.
| | (unreleased) | 1.13 - 1.19 | 5.2 | 6.0, 5.1, 5.0 | 3.10 - 3.14 | | |
| | (unreleased) | 1.13 - 1.19 | 6.0 | 5.2, 5.1, 5.0 | 3.10 - 3.14 | |
There was a problem hiding this comment.
I think we're still closer to 5.2 than we are to fully supporting 6.0, for now.
I'd like to make a release at one point, to put out the "announcement" #2944 to perhaps get more help from the community.
But it's also an option to make a release from a branch, excluding all 6.0 changes.
There was a problem hiding this comment.
It would be ideal to make a release with 5.2 and 3.14 as the last 5.2 release and then move on to 6.0 changes. And make the announcement. But, this will require a new branch with manual cherry-picking of commits.
2 participants
No description provided.