-
-
Notifications
You must be signed in to change notification settings - Fork 27
Support for older pytest #150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
pytest6 is not relevant anymore, we should not keep any support for it. |
Awesome, I'll make a PR :)
…On Fri, 3 May 2024, 18:50 Nikita Sobolev, ***@***.***> wrote:
pytest6 is not relevant anymore, we should not keep any support for it.
Cleaner code, simplier workflow.
—
Reply to this email directly, view it on GitHub
<#150 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA2V5OQ677PW2HBXXX2HJ3ZANFWFAVCNFSM6AAAAABHESWKBCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJSGU4DANJUGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Pytest 7 was released over two years ago, and this repository no longer tests against pytest 6. It should be safe to assume that projects aren't relying on pytest 6 anymore. fixes: typeddjango#150
Pytest 7 was released over two years ago, and this repository no longer tests against pytest 6. It should be safe to assume that projects aren't relying on pytest 6 anymore. fixes: #150
@sobolevn also, speaking of compatibility. Python 3.8 is end of life in later in the year, do you want to keep support for it till then, or is it ok to remove support for it and be able to use PEP 585 in this repo? (Though, in finding that link I noticed that we can already make use of that with a |
Yes, we need 3.8 for now. |
ok, fair enough. The good news is it appears django 5 only supports python 3.10 and above, so I imagine django-stubs could maybe drop it soon? |
yes, we will drop it as soon as it will reach EOL |
Pytest 7 was released over two years ago, and this repository no longer tests against pytest 6. It should be safe to assume that projects aren't relying on pytest 6 anymore. fixes: typeddjango#150
Hi, I'm wondering how important it is to you for this plugin to continue supporting pytest 6?
Is pytest 7/8 are old enough to warrant removing the code that makes this plugin compatible with pytest 6 or would you rather keep that support?
The text was updated successfully, but these errors were encountered: