David Brochart
David Brochart
Thanks for reporting @vwbusguy. Indeed it seems that `traitlets>=5` was required from v1.13.3, and you have v1.13.2. Upgrading should fix it, but you won't be able to install nbgrader.
I don't have your exact environment, but I managed to install `jupyter_server=1.13.2` and `nbgrader` with conda, and `jupyter notebook` starts without error.
When I set the vertices' dtype to `int16` I get the same error. Maybe it is due to deserialization indeed.
I need to find the time, but at first sight it should be doable using https://github.com/CabbageDevelopment/qasync.
Trigger CI.
Trigger CI.
The errors on Mac and Windows seem related to kernel provisioning: ``` if not KPF.instance(parent=self.parent).is_provisioner_available(kspec): > raise NoSuchKernel(kernel_name) E jupyter_client.kernelspec.NoSuchKernel: No such kernel named python3 ``` Maybe @kevin-bates has some...
Thanks Kevin, `--force-reinstall` solved the issue. Now we have these errors on Windows: - `Windows fatal exception: code 0xc0000139` - an apparently empty connection file.
Thanks Kevin for investigating, I think this is getting out of our original scope of checking for any issue with jupyter_client v7.0. I consider we have done enough, and maybe...
@kevin-bates @ccordoba12 thanks, that worked! I don't think we want to merge this PR as-is, as it's testing jupyter_client master. But it can be useful to have it test a...