[issue23778] Add a visual distinction to multiline versionchanged blocks

Demian Brecht added the comment: Sounds good to me. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue23778] Add a visual distinction to multiline versionchanged blocks

R. David Murray added the comment: Yes, exactly, they are supposed to be terse. So I think we should reject this. -- resolution: -> rejected stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue23778] Add a visual distinction to multiline versionchanged blocks

Demian Brecht added the comment: I noted in #2211 that nested lists are supported by Sphinx, so that solves that specific issue. Perhaps it /may/ still be useful to have this though in order to support multiple paragraphs for more detailed change descriptions when needed? That said, I'm not su

[issue23778] Add a visual distinction to multiline versionchanged blocks

R. David Murray added the comment: Heh, you clearly know more about docutils/css than I do. I don't think we want multiple blank delimited paragraphs under a versionchanged directive, though, from a style point of view. A compact unordered list would be best. -- nosy: +georg.brandl,

[issue23778] Add a visual distinction to multiline versionchanged blocks

New submission from Demian Brecht: This came up during #2211, where a multiline versionchanged entry was suggested. Currently, there is no visual distinction between any but the first line of the description and the rest of the body of the docs. The attached patch adds a consistent level of in