-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Markdown 3.4 causes TypeError due to breaking changes #36
Comments
For now I suggest |
I can confirm, I experienced the same problem today. Adding |
Also experiencing the same issue, as is elyra-ai/elyra#2837 |
…wn packages See commentary in this commit, the upstream issue¹, our initial tracking issue² (in another repo), and our Slack thread.³ ¹ ryanfox/sphinx-markdown-tables#36 ² nextstrain/ncov#982 ³ https://bedfordlab.slack.com/archives/C01LCTT7JNN/p1658148441308079
This commit workarounds backward incompatible change introduced in Markdown 3.4 through Python-Markdown/markdown@659a43659 (Update th/td to use style attribute) It addresses error like the following: Extension error (sphinx_markdown_tables): Handler <function process_tables at 0x7f12fd69dc20> for event 'source-read' threw an exception (exception: __init__() missing 1 required positional argument: 'config') See ryanfox/sphinx-markdown-tables#36 and https://python-markdown.github.io/change_log/release-3.4/
This commit workarounds backward incompatible change introduced in Markdown 3.4 through Python-Markdown/markdown@659a43659 (Update th/td to use style attribute) It addresses error like the following: Extension error (sphinx_markdown_tables): Handler <function process_tables at 0x7f12fd69dc20> for event 'source-read' threw an exception (exception: __init__() missing 1 required positional argument: 'config') See ryanfox/sphinx-markdown-tables#36 and https://python-markdown.github.io/change_log/release-3.4/
Because ryanfox/sphinx-markdown-tables#36 was fixed, and now the workaround is actually causing an error
Because ryanfox/sphinx-markdown-tables#36 was fixed, and now the workaround is actually causing an error
If you're now experiencing similar TypeErrors because you worked around this issue by pinning |
Fix was integrated into the official release (ryanfox/sphinx-markdown-tables#36), use that instead of a private patch version (which is no longer available).
Fix was integrated into the official release (ryanfox/sphinx-markdown-tables#36), use that instead of a private patch version (which is no longer available).
Fix was integrated into the official release (ryanfox/sphinx-markdown-tables#36), use that instead of a private patch version (which is no longer available). See Slicer/Slicer@50f807cc1
Markdown 3.4 has just been released and it brings breaking changes to v0.0.15
See Python-Markdown 3.4 Release Notes
Fix required here: https://github.com/ryanfox/sphinx-markdown-tables/blob/master/sphinx_markdown_tables/__init__.py#L24
The text was updated successfully, but these errors were encountered: