When announcing some fields, leastbot shows the python repr, such as this example:
'nathan-at-least' created issue 10 comment 48820217: 'Some revision control convention tie-ins:\r\n\r\n* Branch names should begin with ``${TICKET_NUMBER}.${DESCRIPTION}``, and\r\n'… (truncated)
The \r\n sequences are distracting and probably not too relevant to irc users, so it would be nice if rather than replacing those characters with the python repr replacements, leastbot instead replaces spans of 1 or more whitespace characters with simple space. In that case the above example would look like:
'nathan-at-least' created issue 10 comment 48820217: 'Some revision control convention tie-ins: * Branch names should begin with ``${TICKET_NUMBER}.${DESCRIPTION}``, and '… (truncated)
Note that we should probably keep the python repr translation layer in case weird characters make their way into these fields (such as a nul character). So an implementation would do the whitespace replacement prior to repr.
When announcing some fields, leastbot shows the python
repr
, such as this example:The
\r\n
sequences are distracting and probably not too relevant to irc users, so it would be nice if rather than replacing those characters with the pythonrepr
replacements, leastbot instead replaces spans of 1 or more whitespace characters with simple space. In that case the above example would look like:Note that we should probably keep the python
repr
translation layer in case weird characters make their way into these fields (such as anul
character). So an implementation would do the whitespace replacement prior torepr
.