test: Use latest jupytext==1.0.0 in unit tests

* jupytext==1.0.0 ships sync metamanager along with async. We use sync version in tests Signed-off-by: Mahendra Paipuri <[email protected]>
mwouts · Jul 2, 2024 · f3fbe6e · f3fbe6e
1 parent 7ed811c
commit f3fbe6e
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/pyproject.toml b/pyproject.toml
@@ -75,8 +75,8 @@ test-external = [
   "gitpython",
   "pre-commit",
   # Interaction with other contents managers
-  # jupyter-fs==0.4.0 is async, which is not supported by Jupytext ATM
-  "jupyter-fs<0.4.0"
+  # Starting with jupyter-fs==1.0.0, there is SyncMetaManager available
+  "jupyter-fs==1.0.0"
 ]
 # Coverage requirements
 test-cov = [

diff --git a/tests/external/jupyter_fs/test_jupyter_fs.py b/tests/external/jupyter_fs/test_jupyter_fs.py
@@ -9,11 +9,11 @@
 
 def fs_meta_manager(tmpdir):
     try:
-        from jupyterfs.metamanager import MetaManager
+        from jupyterfs.metamanager import SyncMetaManager
     except ImportError:
         pytest.skip("jupyterfs is not available")
 
-    cm_class = jupytext.build_jupytext_contents_manager_class(MetaManager)
+    cm_class = jupytext.build_jupytext_contents_manager_class(SyncMetaManager)
     logger = logging.getLogger("jupyter-fs")
     cm = cm_class(parent=None, log=logger)
     cm.initResource(