Mercurial > p > roundup > code
view website/issues/html/msg.index.html @ 5650:e8ca7072c629
Fix Python 3 issues in REST code.
* Need to use .get not .getheader for HTTP headers (see hg commit
fec18298ae02, "Python 3 preparation: HTTP headers handling in
roundup_server.py.").
* Need to use key not cmp with sort (see hg commit 3fa026621f69,
"Python 3 preparation: comparisons.").
* dispatch output must be bytes, not str, otherwise writing it to the
socket (e.g. in roundup-server) will fail.
This fixes issues shown up attempting to access the REST interface
with a browser with Python 3 (as opposed to with the Roundup
testsuite, which also has known REST issues with Python 3).
| author | Joseph Myers <jsm@polyomino.org.uk> |
|---|---|
| date | Sun, 17 Mar 2019 16:25:36 +0000 |
| parents | c2d0d3e9099d |
| children |
line wrap: on
line source
<tal:block metal:use-macro="templates/page/macros/icing"> <title metal:fill-slot="head_title" i18n:translate="" >List of messages - <span tal:replace="config/TRACKER_NAME" i18n:name="tracker"/></title> <span metal:fill-slot="body_title" tal:omit-tag="python:1" i18n:translate="">Message listing</span> <td class="content" metal:fill-slot="content"> <table tal:define="batch request/batch" class="messages"> <tr><th colspan=3 class="header" i18n:translate="">Messages</th></tr> <tal:block tal:repeat="msg batch"> <tr> <th><a tal:attributes="href string:msg${msg/id}"><tal:x replace="msg/id"/></a></th> <th tal:content="string:Author: ${msg/author}">author</th> <th tal:content="string:Date: ${msg/date}">date</th> </tr> <tr> <td colspan="3"><pre tal:content="msg/content">content</pre></td> </tr> </tal:block> <metal:block use-macro="templates/issue.index/macros/batch-footer" /> </table> </td> </tal:block>