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 Connection.log for consistency with the logging capability
Address PR review: `Connection.log()` sends the same `notifications/message`
the logging capability covers and `Context.log`'s docstring steers users to it,
so it now carries the same SEP-2577 `@deprecated` marker. Its two test call
sites get `# pyright: ignore[reportDeprecated]`, and the migration guide lists
it among the deprecated logging entry points.
- 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.
1227
+
- Logging: `ServerSession.send_log_message()`, `Connection.log()`, `ClientSession.set_logging_level()`, `Client.set_logging_level()`, and the `MCPServer``Context` helpers `log()`, `debug()`, `info()`, `warning()`, `error()`
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