-
Notifications
You must be signed in to change notification settings - Fork 4
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
3.27.0: pytest is failing in tests/test_basic.py units with deprecation errors #38
Comments
Interesting @henryiii, are the latest sphinx versions not pulled in the CI? This seems like an upstream/dependency issue, but I'm surprised it was not picked up in the CI. @kloczek Can you test with different versions of |
I'm using sphinx with +50% of all my packages [tkloczko@pers-jacek SPECS]$ grep ^%sphinx_build_man python-* | wc -l; ls -1 python-*|wc -l
605
1174 to generate module documentation as man page. It would require check some past build logs from my build infra however IIRC your module had similar pytest issues with sphinx 7.x however as I wrote I'm not ATM 100% and cannot check that today. |
@kloczek Try it out locally on your system with only different sphinx version. The CI does not say which sphinx version it is using: https://github.com/scikit-build/moderncmakedomain/actions/runs/5594294188/job/15153138220, and the traceback indicates that the deprecation warning is coming from But these are also only deprecation warnings, which should only be in the CI, so until that is changed, you can try to manually add that to the ignored warnings: moderncmakedomain/pyproject.toml Line 53 in 0d6b277
|
Looks like sphinx is loading all extensions that are installed, and you've got one that's not updated. It's not modernsphinxdomain's fault (we don't use this method at all), it's only a problem with turning on warnings as errors. The modules we depend on are fine, AFAICT. But if you install other ones (sphinxcontrib.htmlhelp, for example), then Sphinx will produce warnings that become errors when it's loading all entry points. I'm guessing you have one large environment with lots of things installed instead of one just for this package? You can manually ignore there errors there with |
No I have per rpm package build spawned build env in which are only installed only packages listed in rpm BuildRequires (and its dependencies). BuildRequires: python3dist(build)
BuildRequires: python3dist(hatchling)
BuildRequires: python3dist(installer)
BuildRequires: python3dist(wheel)
# ChcekRequires:
BuildRequires: python3dist(docutils)
BuildRequires: python3dist(pygments)
BuildRequires: python3dist(pytest)
BuildRequires: python3dist(setuptools)
BuildRequires: python3dist(sphinx) FYI: |
That was cleared a bit ago: |
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 modulescut off from access to the public network
(pytest is executed with-m "not network"
)Here is pytest output:
Here is list of installed modules in build env
The text was updated successfully, but these errors were encountered: