Isaac Muse

> I'm curious why you chose colons. Personally, they are not my favorite character for this but I don't have any specific reasons why and I don't have any better...

Okay, I just checked out the MkDocs link that uses Multi-Markdown type params. I get what you mean. That is actually what I was doing before importing PyYAML, and what...

Okay, the reference implementation does use increasing levels of colons. It also clearly shows the shorthand parameter format too (`:key: value`): https://myst-parser.readthedocs.io/en/latest/syntax/optional.html#code-fences-using-colons So, as of right now, we are duplicating...

> That being the case, I think the :key: syntax should be out as that is a direct copy of Rest directive syntax. Presumably it is supported in Myst so...

I have a workaround that works pretty well for this. This is **not** a proposed official solution, but a pretty good workaround. I attempted to re-factor fenced blocks as a...

@cgabard, out of curiosity, I tired yours (had to reactor for Python Markdown 2.5.X), but it did not work. Maybe it only works on Python Markdown < 2.5.X? Made be...

I've never used an action for this. I use this: https://github.com/facelessuser/pymdown-extensions/blob/master/.github/workflows/deploy.yml#L30. Seems to work still as I released 10 days ago.

Ah, I forgot that you are running in an org.

I personally don't support Python 2.7 on any new projects if I don't have a direct need. This has been a personal choice as I think it is past time...

I am fully behind dropping 2.7 in 3.2.