AttributeError: module 'mistune' has no attribute 'BlockGrammar' in line 58 of m2r.py #66
Comments
m2r seems to be broken with latest version of mistune see: miyakogi/m2r#66
|
I am getting this as well. Setting |
|
This issue seems to be specific to Python 3.6. With Python 3.8 |
My CI uses the latest 3.9 (via latest Sphinx). |
miyakogi/m2r#66 Signed-off-by: David Galloway <[email protected]>
This temporary change is required to resolve issues in the CI pipeline (docs runner). The change is inspired by miyakogi/m2r#66. [noissue]
miyakogi/m2r#66 Signed-off-by: David Galloway <[email protected]> (cherry picked from commit ed2ad24)
miyakogi/m2r#66 Signed-off-by: David Galloway <[email protected]> (cherry picked from commit ed2ad24)
miyakogi/m2r#66 Signed-off-by: David Galloway <[email protected]> (cherry picked from commit ed2ad24)
miyakogi/m2r#66 Signed-off-by: David Galloway <[email protected]> (cherry picked from commit ed2ad24)
This temporary change is required to resolve issues in the CI pipeline (docs runner). The change is inspired by miyakogi/m2r#66. [noissue]
|
I am facing the same issue right now and it looks like |
|
The PR is waiting to be merged to fix this issue. Seems like this repository is not being maintained anymore. |
Fixing the issue should actually mean fixing the issue. |
|
Just to confirm that even with m2r-0.2.1 and mistune-2.0.0 I get exactly the same result. Complete build log showing all packages used and steps taken to achieve the failed test. |
|
@mcepl I agree that fixing the issue means revamping |
|
Sounds like an m2r3 is needed 😆 |
|
Wait, I have just realised that this is indeed "old" repository and the new "m2r2" is a fork of this repo and being actively maintained here -> https://github.com/CrossNox/m2r2 . They have already have a PR on this issue and hopefully it will be released soon. |
miyakogi/m2r#66 Signed-off-by: David Galloway <[email protected]> (cherry picked from commit ed2ad24)
And again, that PR is not fix just freezing old version of mistune. |
It appears to be unmaintained miyakogi/m2r#66
m2r does not support newest version of mistune: see miyakogi/m2r#66
|
Can you update pypi with this? If I |
Update the Python dependencies on the docs-builder image, to avoid relying on old packages and limit the burden for the next updates of the image. Most packages are updated to their latest version, or to the latest version possible as per the dependency graph. Mistune is pinned to a version < 2.0.0 to fix an issue with m2r (miyakogi/m2r#66), which is pulled as a dependency to sphinxcontrib-openapi. The Makefile for the documentation needs to be updated: the short-name options for sphinx-autobuild seem to have disappeared, leaving the long names only. Signed-off-by: Quentin Monnet <[email protected]>
Update the Python dependencies on the docs-builder image, to avoid relying on old packages and limit the burden for the next updates of the image. Most packages are updated to their latest version, or to the latest version possible as per the dependency graph. Mistune is pinned to a version < 2.0.0 to fix an issue with m2r (miyakogi/m2r#66), which is pulled as a dependency to sphinxcontrib-openapi. The Makefile for the documentation needs to be updated: the short-name options for sphinx-autobuild seem to have disappeared, leaving the long names only. Signed-off-by: Quentin Monnet <[email protected]>
I forked a new project, |
|
I just hit the same issue trying generate |
m2r is unmaintained [0]. It relies on mistune, but is not compatible with mistune versions >= 2.0 [1]. This makes it impossible to update mistune, even though there is a CVE in the package [2]. Switch to sphinx-mdinclude instead. There is also m2r2, but it is not a suitable alternative because they simply force the use of an older mistune version. [0] sphinx-contrib#123 [1] miyakogi/m2r#66 [2] GHSA-fw3v-x4f2-v673 [3] CrossNox/m2r2#43
m2r is unmaintained [0]. It relies on mistune, but is not compatible with mistune versions >= 2.0 [1]. This makes it impossible to update mistune, even though there is a CVE in the old versions of the package [2]. Switch to sphinx-mdinclude instead. There is also m2r2, but it is not a suitable alternative because they simply force the use of an older mistune version [3]. [0] sphinx-contrib#123 [1] miyakogi/m2r#66 [2] GHSA-fw3v-x4f2-v673 [3] CrossNox/m2r2#43
Sphinxcontrib-openapi relies on m2r. But m2r is unmaintained [0]. It relies on mistune, but is not compatible with mistune versions >= 2.0 [1]. This makes it impossible to update mistune, even though there is a CVE in the old versions of the package [2]. Switch to sphinx-mdinclude instead. There is also m2r2, but it is not a suitable alternative because they simply force the use of an older mistune version [3]. [0] sphinx-contrib/openapi#123 [1] miyakogi/m2r#66 [2] GHSA-fw3v-x4f2-v673 [3] CrossNox/m2r2#43 Signed-off-by: Quentin Monnet <[email protected]>
|
Any plans to update |
Sphinxcontrib-openapi relies on m2r. But m2r is unmaintained [0]. It relies on mistune, but is not compatible with mistune versions >= 2.0 [1]. This makes it impossible to update mistune, even though there is a CVE in the old versions of the package [2]. Switch to sphinx-mdinclude instead. There is also m2r2, but it is not a suitable alternative because they simply force the use of an older mistune version [3]. [0] sphinx-contrib/openapi#123 [1] miyakogi/m2r#66 [2] GHSA-fw3v-x4f2-v673 [3] CrossNox/m2r2#43 Signed-off-by: Quentin Monnet <[email protected]>
[ upstream commit 4f893e8 ] Sphinxcontrib-openapi relies on m2r. But m2r is unmaintained [0]. It relies on mistune, but is not compatible with mistune versions >= 2.0 [1]. This makes it impossible to update mistune, even though there is a CVE in the old versions of the package [2]. Switch to sphinx-mdinclude instead. There is also m2r2, but it is not a suitable alternative because they simply force the use of an older mistune version [3]. [0] sphinx-contrib/openapi#123 [1] miyakogi/m2r#66 [2] GHSA-fw3v-x4f2-v673 [3] CrossNox/m2r2#43 Signed-off-by: Quentin Monnet <[email protected]> Signed-off-by: Tobias Klauser <[email protected]>
[ upstream commit 4f893e8 ] Sphinxcontrib-openapi relies on m2r. But m2r is unmaintained [0]. It relies on mistune, but is not compatible with mistune versions >= 2.0 [1]. This makes it impossible to update mistune, even though there is a CVE in the old versions of the package [2]. Switch to sphinx-mdinclude instead. There is also m2r2, but it is not a suitable alternative because they simply force the use of an older mistune version [3]. [0] sphinx-contrib/openapi#123 [1] miyakogi/m2r#66 [2] GHSA-fw3v-x4f2-v673 [3] CrossNox/m2r2#43 Signed-off-by: Quentin Monnet <[email protected]> Signed-off-by: Tobias Klauser <[email protected]>
m2r is unmaintained [0]. It relies on mistune, but is not compatible with mistune versions >= 2.0 [1]. This makes it impossible to update mistune, even though there is a CVE in the old versions of the package [2]. Switch to sphinx-mdinclude instead. There is also m2r2, but it is not a suitable alternative because they simply force the use of an older mistune version [3]. [0] sphinx-contrib#123 [1] miyakogi/m2r#66 [2] GHSA-fw3v-x4f2-v673 [3] CrossNox/m2r2#43 Fixes: sphinx-contrib#123
m2r is unmaintained [0]. It relies on mistune, but is not compatible with mistune versions >= 2.0 [1]. This makes it impossible to update mistune, even though there is a CVE in the old versions of the package [2]. Switch to sphinx-mdinclude instead. There is also m2r2, but it is not a suitable alternative because they simply force the use of an older mistune version [3]. [0] sphinx-contrib#123 [1] miyakogi/m2r#66 [2] GHSA-fw3v-x4f2-v673 [3] CrossNox/m2r2#43 Fixes: sphinx-contrib#123
Needed because m2r does not support newest version of mistune: miyakogi/m2r#66
When packaging new version of mistune (2.0.0-rc1) is included into openSUSE/Factory, this package’s test suite starts failing:
Complete build log with all versions of packages used and steps taken.
The text was updated successfully, but these errors were encountered: