Showing results for 
Search instead for 
Did you mean: 

desktop.ini error in window64 with pyq on jupyter notebook

New Contributor
I am getting following error while loading data from C drive,
The same command works fine if i keep data and jupyter notebook on D drive.
I have also tried to run as administrator but it still fails.

Need to understand following error to troubleshoot.

---------------------------------------------------------------------------error                                     Traceback (most recent call last)<ipython-input-3-062bdf9de0f4> in <module>()      1 ----> 2 get_ipython().run_line_magic('q', '\\l /db/mdata')      3 get_ipython().run_line_magic('q', 'count select from quote where date=2018.07.02')C:\pye\venv\Lib\site-packages\IPython\core\ in run_line_magic(self, magic_name, line, _stack_depth)   2129                 kwargs['local_ns'] = sys._getframe(stack_depth).f_locals   2130             with self.builtin_trap:-> 2131                 result = fn(*args,**kwargs)   2132             return result   2133 C:\pye\venv\Lib\site-packages\pyq\ in q(line, cell, _ns)     58     """     59     if cell is None:---> 60         return pyq.q(line)     61      62     if _ns is None:C:\pye\venv\Lib\site-packages\pyq\ in __call__(self, m, *args)    651         """Execute q code."""    652         try:--> 653             return K._k(0, m, *map(K, args))    654         except TypeError:    655             if m is not None:error: desktop.ini

New Contributor III
Remove desktop.ini from /db/mdata

Thanks Flying, its works after removing desktop.ini file.

I understand that KDB loads everything from by \l command.
It recognized every this owned by q.
KDB should just ignore that is not recognized as q rather throwing error.

Another way to think of it: The directory that you explicitly want q to load should follow the directory structure dictated by the manual. So if you are putting anything extra there, it breaks the system. This is just what "configuration by convention" means.

Another similar issue often happens on MacOS because of .DS_Store files created by Finder.