Skip to content

Update deprecation warning guidance to use FutureWarning#997

Merged
TimMonko merged 2 commits intomainfrom
fix/warnings
Apr 24, 2026
Merged

Update deprecation warning guidance to use FutureWarning#997
TimMonko merged 2 commits intomainfrom
fix/warnings

Conversation

@TimMonko
Copy link
Copy Markdown
Contributor

References and relevant issues

Closes #983

Description

We want to use FutureWarning because it is not silenced by Python

@github-actions github-actions Bot added the documentation Improvements or additions to documentation label Apr 21, 2026
@TimMonko TimMonko added this to the 0.7.1 milestone Apr 21, 2026
@TimMonko
Copy link
Copy Markdown
Contributor Author

cc: @Aniketsy, as I misled you and I'd like us both to learn 😄

@TimMonko TimMonko changed the title Update deprecation warning guidance Update deprecation warning guidance to use FutureWarning Apr 21, 2026
@Aniketsy
Copy link
Copy Markdown
Contributor

I'd like us both to learn 😄

yes 😁 , thanks! for fixing, I was about to ask like, should i fix but then i saw, your PR 😊

@TimMonko TimMonko merged commit 0c43fd3 into main Apr 24, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add FutureWarning as preferred deprecation method to contributing guides

3 participants