-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
py312: latest pytest still throws deprecations warnings with py312 #11515
Comments
As far as I can remember, all py312 PRs were backported and released. But I can double check later.
…On Wed, Oct 18, 2023, at 13:53, Ronny Pfannschmidt wrote:
@bluetech <https://github.com/bluetech> can/should we backport #10894 <#10894> ?
—
Reply to this email directly, view it on GitHub <#11515 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJKW7SYI7TR6PAZXEKG77TX76YKTAVCNFSM6AAAAAA6FJE2ISVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRYGE4TKMRXG4>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
indeed, it was backported |
@ssbarnea they pin a release without python 3.12 support |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At this moment both pytest main branch and latest release (7.4.2) do still produce deprecation warnings when run under pytest 3.12 and that is a problem for anyone that is following the practice of treating warnings as errors during testing.
I already seen projects going the long route of disabling these but the better approach is to address them and ensure that current versions do not produce them.
Example: https://sourcegraph.com/github.com/home-assistant/core/-/blob/pyproject.toml?L495-496
Latest stable version, should not produce any deprecation warnings coming directly from its own code with py312.
The text was updated successfully, but these errors were encountered: