Closed kloczek closed 2 weeks ago
As long as in pyprojecct.toml is requires-python = ">=3.10"
and this unit has name suggests that is is related to python 3.8 I think it is possibility that this unit can be removed.
Pretty sure that this is fixed by 8ea56455aa87feb2d96bf29c335bca5dc885b77b
BTW: because python 3.8 has been EOSed last year this unit can be removed.
What version of
myst-parser
are you using?4.0.0
What version dependencies are you using?
What operating system are you using?
Linux
Describe the Bug
Looks like pytest fails in one unit.
Here is pytest output:
```console + PYTHONPATH=/home/tkloczko/rpmbuild/BUILDROOT/python-myst-parser-4.0.0~no_loopy_deps-2.fc37.x86_64/usr/lib64/python3.10/site-packages:/home/tkloczko/rpmbuild/BUILDROOT/python-myst-parser-4.0.0~no_loopy_deps-2.fc37.x86_64/usr/lib/python3.10/site-packages + /usr/bin/pytest -ra -m 'not network' ==================================================================================== test session starts ==================================================================================== platform linux -- Python 3.10.14, pytest-8.2.2, pluggy-1.5.0 rootdir: /home/tkloczko/rpmbuild/BUILD/MyST-Parser-4.0.0 configfile: pyproject.toml plugins: datadir-1.5.0, sphinx_pytest-0.2.0, regressions-2.5.0, pytest_param_files-0.6.0 collected 1095 items tests/test_anchors.py . [ 0%] tests/test_commonmark/test_commonmark.py .............s...................................................s.s........................................................................ [ 12%] ..................................................................................................................................................................................... [ 29%] ..................................................................................................................................................................................... [ 45%] ................................................................................................................................................... [ 59%] tests/test_docutils.py ........... [ 60%] tests/test_html/test_html_to_nodes.py ................. [ 61%] tests/test_html/test_parse_html.py ..................... [ 63%] tests/test_inventory.py .............. [ 65%] tests/test_renderers/test_error_reporting.py ................... [ 66%] tests/test_renderers/test_fixtures_docutils.py ................................................................................................. [ 75%] tests/test_renderers/test_fixtures_sphinx.py ......................................................................s...........s.s.........s..s................ss.................... [ 88%] ..........s.................F.......... [ 91%] tests/test_renderers/test_include_directive.py ........ [ 92%] tests/test_renderers/test_myst_config.py ........................ [ 94%] tests/test_renderers/test_myst_refs.py ......... [ 95%] tests/test_renderers/test_parse_directives.py ................................. [ 98%] tests/test_sphinx/test_sphinx_builds.py ................. [100%] ========================================================================================= FAILURES ========================================================================================== _________________________________________________________________________________ test_amsmath[38-In list:] _________________________________________________________________________________ file_params = ParamTestData(line=38, title='In list:', description=None, content='- \\begin{equation}\n a = 1\n \\end{equation}\n'... \\end{equation}\n', index=3, fmt=Expected Behavior
pytest should not fail
To Reproduce
I'm packaging your module as an rpm package so I'm using the typical PEP517 based build, install and test cycle used on building packages from non-root account.
python3 -sBm build -w --no-isolation
build
with--no-isolation
I'm using during all processes only locally installed modulesinstaller
modulecut off from access to the public network
(pytest is executed with-m "not network"
)