importing pyxdameraulevenshtein crashes python kernel
See original GitHub issueWindows 10, Python 3.5, pyxdameraulevenshtein v1.5
I get “Kernel died, restarting” anytime i execute this line (in separate venv):
import pyxdameraulevenshtein
Seems like OS issue.
Issue Analytics
- State:
- Created 5 years ago
- Comments:13
Top Results From Across the Web
importing pyxdameraulevenshtein crashes python kernel #11
I have installed it vie pip as the dependency of textdistance package (i opened an issue there but they forwarded me here).
Read more >After conda update, python kernel crashes when matplotlib is ...
I tested this in JupyterLab , PyCharm , and python from the command prompt. ... plotting with matplotlib crashes the python kernel.
Read more >the kernel crashed while executing code in the the current cell ...
I have a conda env with python 3.10.6 and gym==0.23.1. I open a new ipynb in my vscode and run. import gym. env...
Read more >arcgis to_featurelayer() crashes kernel with ImportError ...
My python kernel and ArcGIS both crash when I try to export a spatially ... ImportError: PyCapsule_Import could not import module "datetime".
Read more >Problem with importing monai - vision - PyTorch Forums
I have installed it using pip install monai. and I'm using python 3.9… ... The Kernel crashed while executing code in the the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
1.5.2 was just released, which further addresses the NumPy dependency issue. I think this should solve your problem. I’m going to go ahead and close this issue, but please let me know if you’re still experiencing this problem with 1.5.2.
I just modified
setup.py
a bit to actually remove some NumPy-related code that seemed to be causing various issues. I’ve made the decision to expect the user to explicitly install NumPy prior to installing this library. 1.5.1 is now live on PyPI. I think this will fix your issue. Can you try and let me know?