Skip to content

Consider testing for PendingDeprecationWarnings #2716

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.

Sign up for GitHub

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

Jump to bottom
Open
1ucian0 opened this issue Mar 4, 2025 · 1 comment
Open

Consider testing for PendingDeprecationWarnings #2716

1ucian0 opened this issue Mar 4, 2025 · 1 comment
Assignees
@kaelynj
Labels
content 📄 infra 🏗️ tech debt 💩

Comments

@1ucian0
Copy link
Member

1ucian0 commented Mar 4, 2025

There are many DeprecationWanings coming in 2.1 (see Qiskit/qiskit#13604) Maybe you want to check PendingDeprecationWarnings to be ahead of them?
@javabster javabster added infra 🏗️ needs triage 🤔 this issue needs to be prioritized by the docs team labels Mar 7, 2025
@Eric-Arellano Eric-Arellano changed the title Consider testing for PendingDepreactionWarnings Consider testing for PendingDeprecationWarnings Mar 14, 2025
@Eric-Arellano
Copy link
Collaborator

Great idea! We should treat PendingDeprecationWarnings as just as serious as DeprecationWarning, which errors our notebook tester unless you allow list it.

@Eric-Arellano Eric-Arellano added content 📄 tech debt 💩 and removed needs triage 🤔 this issue needs to be prioritized by the docs team labels Mar 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kaelynj kaelynj

Labels
content 📄 infra 🏗️ tech debt 💩
Projects
Docs Planning
Status: No status
Milestone
No milestone
Development

No branches or pull requests
4 participants
@1ucian0 @Eric-Arellano @javabster @kaelynj