Taneli Hukkinen

> > but we might want to discuss it in another issue in mdformat's issue tracker? > sure wherever :smile: Haha ok lets do this here then. I slightly misunderstood...

Alrighty, here's the new address: https://github.com/executablebooks/mdformat :partying_face:

> I had a look at mdformat and it is not clear how I could ulitize parts of mdformat to create a markdown renderer. This [MDRenderer class](https://github.com/executablebooks/mdformat/blob/b5e44411f88aaab7cc4b7d024133eaa014989b82/src/mdformat/renderer/__init__.py#L27) here is a...

What do you think @chrisjsewell ? If you're worried about the breaking change, we could make the deprecation period very long or infinite.

Great, I can work on this. Do you agree with [this comment](https://github.com/executablebooks/markdown-it-py/pull/190#issuecomment-1021061668) that we should just scrap https://github.com/executablebooks/markdown-it-py/pull/190 ? Or do you want an out-of-range safe wrapper for `src`, something...

Another way to increase performance would be to fill in whatever type annotations that are missing (enforced by the `disallow_untyped_defs = true` mypy setting) and publishing binary wheels built with...

There's a lot to intake here, but I'll start with a question: If there's a JS implementation, why not copy what it does? Are you trying to achieve something that...

Seeing that this PR only removes 4 instances of `try: ... except IndexError:` handling and that almost always we do an `if pos < maximum:` check or similar to ensure...

RTD build will fail because it has these dependencies - `myst-parser` - `markdown-it-py == `, that is since RTD requirements are specified as `pip install .[rtd]`, RTD implicitly has `markdown-it-py`'s...

https://github.com/tsutsu3/uc.micro-py seems like a place where an error like this might have slipped in.