Hi,
I found that under certain circumstances __package__ is not defined and hence FSFinder has no package_prefix set. This leads to an error when trying to import a notebook.
Can it be that this is because __package__ is expected to be the same as spec.parent beginning with Python 3.6?
https://docs.python.org/3/reference/import.html#__package__
Anyway, relying on __package__ seems to be a risk.
Best,
Jens Henrik
...python3.6/site-packages/ipynb-0.5.1-py3.6.egg/ipynb/fs/finder.py in find_spec(self=<ipynb.fs.finder.FSFinder object>, fullname='ipynb.fs.full.job_submit', path=['...site-packages/ipynb-0.5.1-py3.6.egg/ipynb/fs/full'], target=None)
41 Claims modules that are under ipynb.fs
42 """
---> 43 if fullname.startswith(self.package_prefix):
fullname.startswith = <built-in method startswith of str object at 0x7f41805a6580>
self.package_prefix = None
44 for path in self._get_paths(fullname):
45 if os.path.exists(path):
TypeError: startswith first arg must be str or a tuple of str, not NoneType
Hi,
I found that under certain circumstances
__package__is not defined and hence FSFinder has no package_prefix set. This leads to an error when trying to import a notebook.Can it be that this is because
__package__is expected to be the same as spec.parent beginning with Python 3.6?https://docs.python.org/3/reference/import.html#__package__
Anyway, relying on
__package__seems to be a risk.Best,
Jens Henrik