Control: block 1059658 by 1071879 Hi,
I was looking at the RC bug https://bugs.debian.org/1059658, and I noticed that there've been unreleased commits in https://salsa.debian.org/python-team/packages/jupyter-client for months that seem to fix this. However, when I ran the autopkgtests for that version locally I found that they're a mess, with lots of repeats of this (trimmed for readability): jupyter_client/__init__.py:3: in <module> from .asynchronous import AsyncKernelClient jupyter_client/asynchronous/__init__.py:1: in <module> from .client import AsyncKernelClient # noqa jupyter_client/asynchronous/client.py:12: in <module> from ..client import KernelClient, reqrep jupyter_client/client.py:20: in <module> from .connect import ConnectionFileMixin jupyter_client/connect.py:22: in <module> from jupyter_core.paths import jupyter_data_dir, jupyter_runtime_dir, secure_write /usr/lib/python3/dist-packages/jupyter_core/paths.py:208: in <module> deprecation( /usr/lib/python3/dist-packages/jupyter_core/utils/__init__.py:90: in deprecation warnings.warn(message, DeprecationWarning, stacklevel=stacklevel + 1) E DeprecationWarning: Jupyter is migrating its paths to use standard platformdirs E given by the platformdirs library. To remove this warning and E see the appropriate new directories, set the environment variable E `JUPYTER_PLATFORM_DIRS=1` and then run `jupyter --paths`. E The use of platformdirs will be the default in `jupyter_core` v6 _internal = ['jupyter_core/'] internal = 'jupyter_core/' message = 'Jupyter is migrating its paths to use standard platformdirs\ngiven by the platformdirs library. To remove this warni...TER_PLATFORM_DIRS=1` and then run `jupyter --paths`.\nThe use of platformdirs will be the default in `jupyter_core` v6' stacklevel = 2 Now, tests/conftest.py does in fact set JUPYTER_PLATFORM_DIRS=1, so I think the problem is that the autopkgtests run "$py -m pytest jupyter_client" rather than just "$py -m pytest". But that has a different problem: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 865, in import_plugin __import__(importspec) ModuleNotFoundError: No module named 'pytest_jupyter' And: # apt install python3-pytest-jupyter Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: Unsatisfied dependencies: python3-pytest-jupyter : Depends: python3-jupyter-core (>= 5.7) but 5.3.2-2 is to be installed Error: Unable to correct problems, you have held broken packages. So I guess this is https://bugs.debian.org/1071879, and presumably the easiest way out would be to upgrade jupyter-core to a current upstream version. Any objections to me going ahead and doing that? I'm also a bit confused as to how it got this way. Julian must have been able to build pytest-jupyter in order to construct the upload in https://tracker.debian.org/news/1518227/accepted-pytest-jupyter-091-1-source-all-into-unstable/, but a sufficient version of jupyter-core wasn't in unstable then any more than it is now. Was this hacked up locally in some way? Thanks, -- Colin Watson (he/him) [cjwat...@debian.org]
