@mmcky @najuzilu @choldgraf notebooks execute in the same workspace as the artefacts .
Regarding this issue, the artefacts are not the problem, they are properly created with ipython magics and accessed. The problem is the __pycache__ folder which usually gets created with every import statement. In this case, because of the artefacts import statements, I presume..
Now, jupyter-cache specifically checks for artefacts to be a file:-
And in this case, __pycache__ is also passed as an artefact, which breaks the system because it is a folder.
We will need to have some checks on what gets added to the array of paths passed as artefacts to jupyter-cache
Originally posted by @AakashGfude in executablebooks/MyST-NB#122 (comment)
@mmcky @najuzilu @choldgraf notebooks execute in the same workspace as the
artefacts.Regarding this issue, the artefacts are not the problem, they are properly created with
ipython magicsand accessed. The problem is the__pycache__folder which usually gets created with everyimport statement. In this case, because of the artefacts import statements, I presume..Now,
jupyter-cachespecifically checks for artefacts to be a file:-And in this case,
__pycache__is also passed as an artefact, which breaks the system because it is a folder.We will need to have some checks on what gets added to the array of paths passed as artefacts to
jupyter-cacheOriginally posted by @AakashGfude in executablebooks/MyST-NB#122 (comment)