Retrieving informational messages returned by server

(Inspired by this Stack Overflow question.)

Is there a way that we can retrieve informational messages sent by the server, for example, those produced by a PRINT statement in a T-SQL stored procedure?

For a test SP

USE [myDb]
GO

/****** Object:  StoredProcedure [dbo].[PrintTest]    Script Date: 2018-12-14 10:59:12 ******/
SET ANSI_NULLS ON
GO

SET QUOTED_IDENTIFIER ON
GO

-- =============================================
-- Author:		gord
-- Create date: 
-- Description:	
-- =============================================
ALTER PROCEDURE [dbo].[PrintTest] 
AS
BEGIN
    SET NOCOUNT ON;
    PRINT 'no es bueno';
END

GO

the message does appear in the ODBC trace

main            1c0c-18b0	ENTER SQLExecDirectW 
        HSTMT               0x000000000040DFA0
        WCHAR *             0x0000000002F52830 [      18] "EXEC dbo.PrintTest"
        SDWORD                    18

main            1c0c-18b0	EXIT  SQLExecDirectW  with return code 1 (SQL_SUCCESS_WITH_INFO)
        HSTMT               0x000000000040DFA0
        WCHAR *             0x0000000002F52830 [      18] "EXEC dbo.PrintTest"
        SDWORD                    18

        DIAG [01000] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]no es bueno (0) 

but is there a way we can retrieve it in our Python script?

[matthewgdv]

Is this still being looked at? This would be dead useful for me, as my organization uses stored procs all over the place that feed back information about the success/failure state of the subprocedures they call as print statements rather than raising errors, since an error would kill the whole thing. I currently have no way of finding out what a proc actually did when I call it using pyodbc.

[jerrycl]

I agree this would be a great feature.

PEP-249 specifies an Optional DB API Extension, of Cursor.messages, which would contain a list of tuples (exception class, exception value). This is a bit different from the list of tuples [(SqlState,Msg,NativeError)] proposed above, but the SqlState and the NativeError could be put into the exception class.