Closed mahendrapaipuri closed 2 months ago
Hi @mahendrapaipuri , yes that's correct, I have not made significant progress on the async contents manager. From what I remember the impact was very big and I did not identify a big demand for that. Of course I am happy to reconsider and restart that work!
Yes I did saw the incompatibility between jupytext
and recent version of jupyter-fs
(there's a test on the CI in which I had to pin the version of jupyter-fs
). It's a great news that now jupyter-fs
has a sync contents manager! If I understand correctly, you're suggesting that we document how to use jupytext
with that sync contents manager in its latest version? That would be great!
Well, we should clearly document the compatbility with jupyter-fs
. Moreover, I think we need to improve this code here. In the case of jupyter-fs
there is no Async
in its class name (its MetaManager
) and so, the warning will never be triggered (I guess).
We should look into base classes (the classes that current contents manager has dervied from) and check if they are based on sync
or async
variants and emit the logs. Maybe using inspect
can be used to check the base classes.
What do you think?
jupyter-fs 1.0.0
has landed last week and now it usesAsyncContentsManager
by default in itsMetaManager
. When used along withjupytext
, this will be broken asjupytext
, for the moment, only supports syncContentsManager
. There is a stale PR #1021 that attempts to addAsyncContentsManager
support tojupytext
but has not progressed in a while.Probably we should document clearly that
jupytext
is only compatible withSyncMetaManager
ofjupyter-fs
that has been added in1.0.0
. In factjupytef-fs>0.3.1
usesAsyncContentsManager
by default andSyncMetaManager
is only added in1.0.0
. So, I guess for thejupyter-fs
versions0.4.0
and0.4.1
,jupytext
is not compatible.@mwouts Did you have an opportunity to look into it? Cheers!