sphinx-build defaults to the 'tabulary' environment for tables,
but uses regular 'tabular' for those involving literal blocks,
since tabulary does not handle them properly. It seems that this
deficiency of tabulary also applies to inline literals, which
are rendered as \code{} sections by the latex builder.
Fortunately, sphinx provides a workaround to force a particular
column specification for the table.
The requirement for a table:: statement after the tabularcolumns::
statement is very poorly documented.
ticket: 7447
tags: pullup
target_version: 1.11
Differences between Heimdal and MIT Kerberos API
================================================
+.. tabularcolumns:: |l|l|
+
+.. table::
======================================== =================================================
:c:func:`krb5_auth_con_getaddrs()` H5l: If either of the pointers to local_addr