FIX: expose Edb deprecations statically for grpc and dotnet backends#1980
Merged
svandenb-dev merged 10 commits intomainfrom Apr 2, 2026
Merged
FIX: expose Edb deprecations statically for grpc and dotnet backends#1980svandenb-dev merged 10 commits intomainfrom
svandenb-dev merged 10 commits intomainfrom
Conversation
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Duplication | 11 |
TIP This summary will be updated as you push new changes. Give us feedback
…statric-deprecation-aware # Conflicts: # tests/integration/test_edb_deprecation_metadata.py
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #1980 +/- ##
===========================================
- Coverage 70.20% 48.93% -21.28%
===========================================
Files 261 263 +2
Lines 42416 43069 +653
===========================================
- Hits 29779 21074 -8705
- Misses 12637 21995 +9358 🚀 New features to boost your workflow:
|
maxcapodi78
approved these changes
Apr 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR makes deprecated PyEDB APIs visible to static analysis tools and IDEs across the package, while preserving the existing runtime deprecation warnings.
The original issue was first observed with top-level backend selection:
In this case, deprecation warnings were active at runtime, but PyCharm did not show methods like save_edb() as deprecated.
Root cause
PyEDB already had runtime deprecation decorators:
However, those decorators only emitted warnings at runtime and did not provide a standard static deprecation path for IDEs/type checkers.
There was also a typing aspect:
What changed
Updated the shared deprecation helpers in:
so that deprecated symbols expose static deprecation metadata in addition to runtime warnings.
This allows existing deprecated APIs across the package to benefit from a centralized solution rather than patching each file independently.
Updated:
so the overloads resolve directly to the concrete backend classes:
This improves IDE inference for top-level usage:
and makes backend-specific deprecated members discoverable.
3. Backend-specific deprecated APIs
Added static deprecation coverage for deprecated Edb APIs in:
Added and extended integration coverage in:
closes #1981