Closed eepgwde closed 5 years ago
Why are you using ~/q/l32/q python.q
instead of pyq
command? I see you're not using virtual environment, and it seems that you use modified version of PyQ, as 4.1.4 does not support python 3.7.
pyq and ipyq do work for me with python 3.7. It's just the linkage with jupyter notebook that doesn't work.
There's no guidance on what the pyq_3/kernel.json file should contain.
You mentioned using pyq. I don't know what you were referring to. This command is the only one I mentioned, it fails with pyq.
~/q/l32/q python.q -mpyq.kernel install --user
You mentioned using a virtual environment. I stated that I use anaconda.
I found out that pyq can't get around the GIL, so the q component is only useful as a blocked client, so I'll have to run q as a separate process anyway.
You mentioned using a virtual environment. I stated that I use anaconda.
Anaconda != virtual environment. Please follow guide on setting up PyQ in the virtual environment in order to troubleshoot the issue.
It's just the linkage with jupyter notebook that doesn't work.
It's a known issue — see #99 for workaround.
There's no guidance on what the pyq_3/kernel.json file should contain.
You shouldn't touch that file. You need to install Jupyter kernel using following commands:
pip install pyq-kernel
pyq -m pyq.kernel install
You mentioned using pyq. I don't know what you were referring to.
pyq
is command for starting PyQ.
Questions
[ ] Which operating system are you using (if Linux, please provide flavour of it, i.e RedHat, CentOS or Ubuntu), is it 32-bit, or 64-bit?
[ ] Which version of PyQ are you running? Please provide output of
pyq --versions
, if PyQ isn't operational, please provide Python interpreter version and PyQ versionpython -V; python3 -V; pip list | grep pyq
:[ ] Which version of kdb+ are you using, is it 32-bit or 64-bit?
[ ] If on 64-bit, is your
QLIC
set? Please provide outputenv | grep QLIC
on linux/macOS, orset|grep QLIC
on Windows.[ ] Did you use virtual environment to install PyQ? If not, why?
[ ] Where is your
QHOME
? Please provide outputenv | grep QHOME
on linux/macOS, orset|grep QHOME
on Windows.[ ] Do you use Conda? If so, what version?
Steps to reproduce the issue
This returns
I used the -user option to get the kernel spec file
~/.local/share/jupyter/kernels/pyq_3/kernel.json
And that contains:
Only when I changed the entries, would Jupyter make an attempt to start and
Expected result
I'm hoping for the ipyq Kernel to start up in the Jupyter notebook.
Actual result
Five attempts at this 0;IPython: dash0/plotly^GThe autoreload extension is already loaded. To reload it, use: %reload_ext autoreload And then
Workaround
If you know workaround, please provide it here.