Skip to content

Fix for #56716: Use assert_produces_warning instead of pytest.raises to show FutureWarning #56722

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

Closed
wants to merge 14 commits into from

Conversation

pmhatre1
Copy link
Contributor

@pmhatre1 pmhatre1 commented Jan 3, 2024

@pmhatre1
Copy link
Contributor Author

pmhatre1 commented Jan 3, 2024

I solved my earlier PR on my main branch which is still open and updated all the code to this branch during commit. I will be careful hereon to create branches for new feature/bug. Any help so that the code in my main branch won't be reflected here.I am new and currently learning git.

@mroeschke
Copy link
Member

Closed by #56974

@mroeschke mroeschke closed this Jan 23, 2024
@pmhatre1 pmhatre1 deleted the new_clean_56716 branch January 29, 2024 19:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CLN: Use assert_produces_warning instead of pytest.raises to show FutureWarning
2 participants