Convert README to Markdown

Also add reference to the Rust crate.

.github/workflows/main.yml

@@ -1,17 +1,17 @@
 name: Tests
 on:
   push:
-    branches: [ master ]
+    branches: [master]
   pull_request:
-    branches: [ master ]
+    branches: [master]
 jobs:
   tests:
     name: tests-python${{ matrix.python-version }}-${{ matrix.os }}
     runs-on: ${{ matrix.os }}
     strategy:
       matrix:
-        python-version: ['3.8', '3.9', '3.10', '3.11', '3.12', 'pypy3.9']
-        os: ['ubuntu-latest']
+        python-version: ["3.8", "3.9", "3.10", "3.11", "3.12", "pypy3.9"]
+        os: ["ubuntu-latest"]
     steps:
       - uses: actions/checkout@v4
       - name: Set up Python ${{ matrix.python-version }}
@@ -35,9 +35,10 @@ jobs:
         run: make check
       - name: Run make distcheck
         run: make distcheck
-      - name: Docs build
-        run: rst2html.py README.rst README.html
-        if: "matrix.python-version == '3.8'"
-      - name: Docs build
-        run: rst2html README.rst README.html
-        if: "matrix.python-version != '3.8'"
+    # Disabled; needs a tuit or two
+    #   - name: Docs build
+    #     run: md2html.py README.md README.html
+    #     if: "matrix.python-version == '3.8'"
+    #   - name: Docs build
+    #     run: md2html README.md README.html
+    #     if: "matrix.python-version != '3.8'"

Makefile.am

@@ -5,7 +5,7 @@ EXTRA_DIST =  \
 	INSTALL \
 	Makefile.am \
 	NEWS \
-	README.rst \
+	README.md \
 	all_tests.py \
 	c++/README \
 	c/README \

README.rst → README.md

@@ -15,8 +15,7 @@
 
   See the COPYING file for full details on the licensing of Subunit.
 
-Subunit
--------
+# Subunit
 
 Subunit is a streaming protocol for test results.
 
@@ -69,16 +68,15 @@ Subunit supplies the following filters:
  * subunit-stats - generate a summary of a subunit stream.
  * subunit-tags - add or remove tags from a stream.
 
-Integration with other tools
-----------------------------
+## Integration with other tools
+
 
 Subunit's language bindings act as integration with various test runners like
 'check', 'cppunit', Python's 'unittest'. Beyond that a small amount of glue
 (typically a few lines) will allow Subunit to be used in more sophisticated
 ways.
 
-Python
-======
+### Python
 
 Subunit has excellent Python support: most of the filters and tools are written
 in python and there are facilities for using Subunit to increase test isolation
@@ -92,21 +90,24 @@ subunit via the ``subunit.run`` module::
 For more information on the Python support Subunit offers , please see
 ``pydoc subunit``, or the source in ``python/subunit/``
 
-C
-=
+### Rust
+
+There is a rust crate [subunit](https://crates.io/crates/subunit) that can be used to parse v1 and v1, and emit v2 subunit streams.
+
+
+### C
 
 Subunit has C bindings to emit the protocol. The 'check' C unit testing project
 has included subunit support in their project for some years now. See
 'c/README' for more details.
 
-C++
-===
+### C++
+
 
 The C library is includable and usable directly from C++. A TestListener for
 CPPUnit is included in the Subunit distribution. See 'c++/README' for details.
 
-shell
-=====
+### shell
 
 There are two sets of shell tools. There are filters, which accept a subunit
 stream on stdin and output processed data (or a transformed stream) on stdout.
@@ -116,16 +117,14 @@ consisting of simple functions to output protocol elements, and a patch for
 adding subunit output to the 'ShUnit' shell test runner. See 'shell/README' for
 details.
 
-Filter recipes
---------------
+#### Filter recipes
 
 To ignore some failing tests whose root cause is already known::
 
   subunit-filter --without 'AttributeError.*flavor'
 
+## The xUnit test model
 
-The xUnit test model
---------------------
 
 Subunit implements a slightly modified xUnit test model. The stock standard
 model is that there are tests, which have an id(), can be run, and when run
@@ -136,16 +135,15 @@ a runner has without running them), tags (allow users to describe tests in
 ways the test framework doesn't apply any semantic value to), file attachments
 (allow arbitrary data to make analysing a failure easy) and timestamps.
 
-The protocol
-------------
+## The protocol
+
 
 Version 2, or v2 is new and still under development, but is intended to
 supercede version 1 in the very near future. Subunit's bundled tools accept
 only version 2 and only emit version 2, but the new filters subunit-1to2 and
 subunit-2to1 can be used to interoperate with older third party libraries.
 
-Version 2
-=========
+### Version 2
 
 Version 2 is a binary protocol consisting of independent packets that can be
 embedded in the output from tools like make - as long as each packet has no
@@ -248,38 +246,32 @@ the version check due to coincidence.
 
 Flags are stored in network byte order too.
 
+```asciiart
 +------------+------------+------------------------+
 | High byte               | Low byte               |
 +------------+------------+------------------------+
 | 15 14 13 12 11 10  9  8 | 7  6  5  4  3  2  1  0 |
 +------------+------------+------------------------+
 | VERSION    |      feature bits                   |
 +------------+-------------------------------------+
+```
 
 Valid version values are:
-0x2 - version 2
+`0x2` - version 2
 
 Feature bits:
 
-+---------+-------------+---------------------------+
-| Bit 11  | mask 0x0800 | Test id present.          |
-+---------+-------------+---------------------------+
-| Bit 10  | mask 0x0400 | Routing code present.     |
-+---------+-------------+---------------------------+
-| Bit  9  | mask 0x0200 | Timestamp present.        |
-+---------+-------------+---------------------------+
-| Bit  8  | mask 0x0100 | Test is 'runnable'.       |
-+---------+-------------+---------------------------+
-| Bit  7  | mask 0x0080 | Tags are present.         |
-+---------+-------------+---------------------------+
-| Bit  6  | mask 0x0040 | File content is present.  |
-+---------+-------------+---------------------------+
-| Bit  5  | mask 0x0020 | File MIME type is present.|
-+---------+-------------+---------------------------+
-| Bit  4  | mask 0x0010 | EOF marker.               |
-+---------+-------------+---------------------------+
-| Bit  3  | mask 0x0008 | Must be zero in version 2.|
-+---------+-------------+---------------------------+
+| Bit position | Mask | Description|
+|---------|-------------|---------------------------|
+| Bit 11  |  `0x0800` | Test id present.          |
+| Bit 10  |  `0x0400` | Routing code present.     |
+| Bit  9  |  `0x0200` | Timestamp present.        |
+| Bit  8  |  `0x0100` | Test is 'runnable'.       |
+| Bit  7  |  `0x0080` | Tags are present.         |
+| Bit  6  |  `0x0040` | File content is present.  |
+| Bit  5  |  `0x0020` | File MIME type is present.|
+| Bit  4  |  `0x0010` | EOF marker.               |
+| Bit  3  |  `0x0008` | Must be zero in version 2.|
 
 Test status gets three bits:
 Bit 2 | Bit 1 | Bit 0 - mask 0x0007 - A test status enum lookup:
@@ -348,8 +340,7 @@ to be '0/3'.
 Following the end of the packet is a CRC-32 checksum of the contents of the
 packet including the signature.
 
-Example packets
-~~~~~~~~~~~~~~~
+#### Example packets
 
 Trivial test "foo" enumeration packet, with test id, runnable set,
 status=enumeration. Spaces below are to visually break up signature / flags /
@@ -358,15 +349,15 @@ length / testid / crc32
 b3 2901 0c 03666f6f 08555f1b
 
 
-Version 1 (and 1.1)
-===================
+### Version 1 (and 1.1)
 
 Version 1 (and 1.1) are mostly human readable protocols.
 
-Sample subunit wire contents
-----------------------------
+#### Sample subunit wire contents
 
-The following::
+The following:
+
+```subunit
 
   test: test foo works
   success: test foo works
@@ -389,18 +380,18 @@ When run through subunit2pyunit::
   ..
   ]..  space is eaten.
   foo.c:34 WARNING foo is not defined.
+```
 
-
-Subunit v1 protocol description
-===============================
+#### Subunit v1 protocol description
 
 This description is being ported to an EBNF style. Currently its only partly in
 that style, but should be fairly clear all the same. When in doubt, refer the
 source (and ideally help fix up the description!). Generally the protocol is
 line orientated and consists of either directives and their parameters, or
 when outside a DETAILS region unexpected lines which are not interpreted by
-the parser - they should be forwarded unaltered::
+the parser - they should be forwarded unaltered:
 
+```ebnf
     test|testing|test:|testing: test LABEL
     success|success:|successful|successful: test LABEL
     success|success:|successful|successful: test LABEL DETAILS
@@ -430,6 +421,7 @@ the parser - they should be forwarded unaltered::
     PART_BYTES ::= (DIGITS CR LF BYTE{DIGITS})* '0' CR LF
     LF ::= '\n'
     CR ::= '\r'
+```
 
 unexpected output on stdout -> stdout.
 exit w/0 or last test completing -> error
@@ -477,11 +469,9 @@ tests in some frameworks). uxsuccess is used to indicate and unexpected success
 where a test though to be failing actually passes. It is complementary to
 xfail.
 
-Hacking on subunit
-------------------
+## Hacking on subunit
 
-Releases
-========
+### Releases
 
 * Update versions in configure.ac and python/subunit/__init__.py.
 * Update NEWS.

pyproject.toml

@@ -1,48 +1,47 @@
 [build-system]
-requires = ["setuptools>=61.2", "testtools", "iso8601"]
 build-backend = "setuptools.build_meta"
+requires = ["iso8601", "setuptools>=61.2", "testtools"]
 
 [tool.ruff]
 line-length = 120
 
 [project]
-name = "python-subunit"
-description = "Python implementation of subunit test streaming protocol"
-readme = "README.rst"
+authors = [
+    { name = "Robert Collins", email = "subunit-dev@lists.launchpad.net" },
+]
 classifiers = [
     "Intended Audience :: Developers",
     "Operating System :: OS Independent",
-    "Programming Language :: Python",
     "Programming Language :: Python :: 3",
-    "Programming Language :: Python :: 3.8",
-    "Programming Language :: Python :: 3.9",
     "Programming Language :: Python :: 3.10",
     "Programming Language :: Python :: 3.11",
     "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.8",
+    "Programming Language :: Python :: 3.9",
+    "Programming Language :: Python",
     "Topic :: Software Development :: Testing",
 ]
-keywords = ["python", "test", "streaming"]
-authors = [{name = "Robert Collins", email = "subunit-dev@lists.launchpad.net"}]
-license = {text = "Apache-2.0 or BSD"}
-dependencies = [
-    "iso8601",
-    "testtools>=0.9.34",
-]
-requires-python = ">=3.8"
+dependencies = ["iso8601", "testtools>=0.9.34"]
+description = "Python implementation of subunit test streaming protocol"
 dynamic = ["version"]
+keywords = ["python", "streaming", "test"]
+license = { text = "Apache-2.0 or BSD" }
+name = "python-subunit"
+readme = "README.md"
+requires-python = ">=3.8"
 
 [project.urls]
-Homepage = "http://launchpad.net/subunit"
 "Bug Tracker" = "https://bugs.launchpad.net/subunit"
+Homepage = "http://launchpad.net/subunit"
 "Source Code" = "https://github.com/testing-cabal/subunit/"
 
 [project.optional-dependencies]
 "docs" = ["docutils"]
-"test" = ["fixtures", "testscenarios", "hypothesis"]
+"test" = ["fixtures", "hypothesis", "testscenarios"]
 
 [tool.setuptools.packages.find]
-where = ["python"]
 include = ["subunit*"]
+where = ["python"]
 
 [project.scripts]
 "subunit-1to2" = "subunit.filter_scripts.subunit_1to2:main"
@@ -61,7 +60,7 @@ include = ["subunit*"]
 "tap2subunit" = "subunit.filter_scripts.tap2subunit:main"
 
 [tool.setuptools.dynamic]
-version = {attr = "subunit.version_string"}
+version = { attr = "subunit.version_string" }
 
 [tool.setuptools]
 license-files = ["COPYING"]