You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deprecate only Context.log for logging, with a capability-level message
The `debug`/`info`/`warning`/`error` convenience helpers delegate to
`Context.log`, so deprecating `log` alone covers them - they warn through it
instead of each carrying their own marker. Drop their `@deprecated` decorators
and the now-stale `# pyright: ignore[reportDeprecated]` on their call sites.
Reword every logging deprecation ("The logging capability is deprecated as of
...") so the message names the feature rather than the individual method, and
widen the `filterwarnings` pattern to match the new wording.
- Logging: `ServerSession.send_log_message()`, `ClientSession.set_logging_level()`, `Client.set_logging_level()`, and the `MCPServer``Context` helpers `log()`, `debug()`, `info()`, `warning()`, `error()`
1227
+
- Logging: `ServerSession.send_log_message()`, `ClientSession.set_logging_level()`, `Client.set_logging_level()`, and `MCPServer``Context.log()`. The `Context.debug()` / `info()` / `warning()` / `error()` helpers delegate to `log()`, so they warn through it rather than carrying their own marker.
1228
1228
1229
1229
The runtime warning is emitted as `mcp.MCPDeprecationWarning`, which subclasses `UserWarning` (not `DeprecationWarning`) so it is visible by default. To silence it, filter that category:
0 commit comments